View PM8313-RI_1426939.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer pmc-sierra, inc. 105 - 8555 baxter place burnaby, bc canada v5a 4v7 604 .415.6000 pm8313 d3mx m13 multiplexer issue 5: july 1998
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer pmc-sierra, inc. 105 - 8555 baxter place burnaby, bc canada v5a 4v7 604 .415.6000
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer i contents 1 features ...................................................................................................................... ..1 2 applications .................................................................................................................6 3 standard references ..............................................................................................7 4 application example..................................................................................................9 5 block diagram ...........................................................................................................10 6 pin diagram .................................................................................................................13 7 pin description .........................................................................................................14 8 functional description ........................................................................................34 8.1 ds3 framer.....................................................................................................34 8.2 ds3 performance monitor ......................................................................36 8.3 path maintenance data link receiver ..................................................37 8.4 alarm and control channel bit oriented code detector........37 8.5 ds3 transmitter...........................................................................................38 8.6 path maintenance data link transmitter ...........................................38 8.7 alarm and control channel bit oriented code transmitter ..39 8.8 m23 multiplexer ...........................................................................................39 8.9 ds2 framer.....................................................................................................40 8.10 m12 multiplexer ...........................................................................................42 8.11 loopback modes ..........................................................................................43 8.12 microprocessor interface ....................................................................46 9 register memory map.............................................................................................47 10 normal mode register description.................................................................51 10.1 ds3 pmon registers ...................................................................................75
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer ii 11 test features description ................................................................................132 11.1 test mode register memory map........................................................132 11.2 test mode 0 ..................................................................................................137 12 operation ..................................................................................................................14 1 12.1 using the internal data link transmitter .......................................141 12.2 using the internal data link receiver ..............................................142 12.2.1 key used on subsequent diagrams: .....................................145 13 functional timing...................................................................................................150 14 absolute maximum ratings .................................................................................158 15 d.c. characteristics..............................................................................................159 16 microprocessor interface timing characteristics...............................161 17 d3mx timing characteristics.............................................................................166 18 ordering and thermal information ...............................................................179 19 mechanical information......................................................................................180
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer iii list of registers register 00h: master reset / clock status.................................................................52 register 01h: revision/global pmon update...............................................................54 register 02h: master bypass configuration..............................................................55 register 03h: master hdlc configuration..................................................................57 register 04h: master loopback configuration........................................................59 register 05h: master interface configuration .......................................................61 register 06h: master alarm enable/network requirement bit .........................63 register 07h: master test .................................................................................................66 register 08h: master interrupt source #1 ................................................................68 register 09h: master interrupt source #2 ................................................................70 register 0ah: master interrupt source #3 ................................................................71 register 0ch:ds3 tran configuration ..........................................................................72 register 0dh:ds3 tran diagnostic .................................................................................74 register 11h: ds3 pmon interrupt enable/status.....................................................76 register 14h: ds3 lcv count lsb......................................................................................77 register 15h: ds3 lcv count msb.....................................................................................77 register 16h: ds3 ferr count lsb...................................................................................78 register 17h: ds3 ferr count msb..................................................................................78 register 18h: ds3 exzs count lsb ...................................................................................79 register 19h: ds3 exzs count msb ..................................................................................79 register 1ah: ds3 perr count lsb ..................................................................................80 register 1bh: ds3 perr count msb .................................................................................80 register 1ch: ds3 cperr count lsb ...............................................................................81
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer iv register 1dh: ds3 cperr count msb ..............................................................................81 register 1eh: ds3 febe count lsb...................................................................................82 register 1fh: ds3 febe count msb ..................................................................................82 register 20h: xfdl tsb configuration ..........................................................................83 register 21h: xfdl tsb interrupt status......................................................................85 register 22h: xfdl tsb transmit data.............................................................................86 register 24h: rfdl tsb configuration ..........................................................................87 register 25h: rfdl tsb interrupt control/status...................................................88 register 26h: rfdl tsb status...........................................................................................90 register 27h: rfdl tsb receive data...............................................................................92 register 28h: mx23 configuration ..................................................................................93 register 29h: mx23 demux ais insert register...........................................................95 register 2ah: mx23 mux ais insert register ...............................................................96 register 2bh: mx23 loopback activate register.......................................................97 register 2ch: mx23 loopback request insert register........................................98 register 2dh: mx23 loopback request detect register ......................................99 register 2eh: mx23 loopback request interrupt register ..............................100 register 31h: feac xboc tsb code ................................................................................101 register 32h: rboc configuration/interrupt enable ..........................................102 register 33h: rboc interrupt status ..........................................................................103 register 34h: ds3 frmr configuration .......................................................................103 register 35h: ds3 frmr interrupt enable (ace=0) ..................................................106 register 35h: ds3 frmr additional configuration register (ace=1) ..............108 register 36h: ds3 frmr interrupt status ..................................................................111
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer v register 37h: ds3 frmr status........................................................................................113 registers 40h, 50h, 60h, 70h, 80h, 90h and a0h: ds2 frmr configuration .........115 registers 41h, 51h, 61h, 71h, 81h, 91h and a1h: ds2 frmr interrupt enable ...117 registers 42h, 52h, 62h, 72h, 82h, 92h and a2h: ds2 frmr interrupt status ....118 registers 43h, 53h, 63h, 73h, 83h, 93h and a3h: ds2 frmr status..........................119 registers 44h, 54h, 64h, 74h, 84h, 94h and a4h: ds2 frmr monitor interrupt enable/status...........................................................................................................121 registers 45h, 55h, 65h, 75h, 85h, 95h and a5h: ds2 frmr ferr count ...............123 registers 46h, 56h, 66h, 76h, 86h, 96h and a6h: ds2 frmr perr count (lsb).....124 registers 47h, 57h, 67h, 77h, 87h, 97h and a7h: ds2 frmr perr count (msb)....124 registers 48h, 58h, 68h, 78h, 88h, 98h and a8h: mx12 configuration and control .....................................................................................................................125 registers 49h, 59h, 69h, 79h, 89h, 99h and a9h: mx12 loopback code select register.....................................................................................................................12 7 registers 4ah, 5ah, 6ah, 7ah, 8ah, 9ah and aah: mx12 ais insert register......129 registers 4bh, 5bh, 6bh, 7bh, 8bh, 9bh and abh: mx12 loopback activate register.....................................................................................................................13 0 registers 4ch, 5ch, 6ch, 7ch, 8ch, 9ch and ach: mx12 loopback interrupt register.....................................................................................................................13 1
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer vi list of figures figure 1 - m1-3 multiplexer/demultiplexer...............................................................9 figure 2 - ds3 diagnostic loopback ..........................................................................44 figure 3 - ds3 line loopback ........................................................................................45 figure 4 - ds2/g.747 demultiplex loopback .............................................................45 figure 5 - ds1/e1 demultiplex loopback ..................................................................46 figure 6 - typical data frame .....................................................................................145 figure 7 - rfdl normal data and abort sequence.............................................146 figure 8 - rfdl fifo overrun......................................................................................147 figure 9 - xfdl normal data sequence...................................................................148 figure 10 - xfdl underrun sequence .......................................................................149 figure 11 - receive ds3 high speed output timing...............................................150 figure 12 - receive ds3 low speed timing................................................................151 figure 13 - transmit ds3 timing ...................................................................................152 figure 14 - tdlint timing - normal data transmission .........................................153 figure 15 - tdleomi timing - with removal of tdleomi before completion of fcs transmission....................................................................................................154 figure 16 - tdleomi timing - with removal of tdleomi after completion of fcs transmission....................................................................................................155 figure 17 - input ds3 overhead serial stream .....................................................156 figure 18 - output ds3 overhead serial stream .................................................157 figure 19 - microprocessor read access timing ................................................162 figure 20 - microprocessor write access timing...............................................164 figure 21 - receive ds3 input timing ..........................................................................166 figure 22 - transmit ds3 input timing........................................................................167
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer vii figure 23 - transmit overhead input timing...........................................................168 figure 24 - transmit tributary input timing ...........................................................169 figure 25 - transmit data link input timing .............................................................170 figure 26 - transmit data link eom input timing ....................................................171 figure 27 - transmit ds3 output timing....................................................................172 figure 28 - receive ds3 output timing ......................................................................174 figure 29 - receive overhead output timing .........................................................176 figure 30 - transmit overhead output timing.......................................................177 figure 31 - receive tributary output timing .........................................................177 figure 32 - receive data link output timing............................................................178 figure 33 - 208 pin copper leadframe plastic quad flat pack (r suffix): ...180
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer viii list of tables table 1 - test mode address locations C read from inputs.......................138 table 2 - test mode address locations C write to outputs ......................138 table 3 - transmitt overhead format ..................................................................156 table 4 - receive overhead format.......................................................................157 table 5 - d3mx absolute maximum ratings ..........................................................158 table 6 - d3mx d.c. characteristics.......................................................................159 table 7 - microprocessor read access (figure 19) .......................................161 table 8 - microprocessor write access (figure 20) ......................................163 table 9 - d3mx receive ds3 input (figure 21) ......................................................166 table 10 - d3mx transmit ds3 input (figure 22) ....................................................167 table 11 - d3mx transmit overhead input (figure 23) .......................................168 table 12 - d3mx transmit tributary input (figure 24) .......................................169 table 13 - d3mx transmit data link input (figure 25)..........................................170 table 14 - d3mx transmit data link eom input (figure 26) ................................171 table 15 - d3mx transmit ds3 output (figure 27) ................................................172 table 16 - d3mx receive ds3 output (figure 28) ..................................................173 table 17 - d3mx receive overhead output (figure 29) .....................................175 table 18 - d3mx transmit overhead output (figure 30) ...................................176 table 19 - d3mx receive tributary output (figure 31) ......................................177 table 20 - d3mx receive data link output (figure 32) ........................................177 table 21 - d3mx ordering information...................................................................179 table 22 - d3mx thermal information .....................................................................179
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 1 1 features integrates a full featured m13 multiplexer and ds-3 framer in a single monolithic device. supports the m23 or c-bit parity ds3 formats. supports the m12 or g.747 formats allowing ds1 or e1 signals to be multiplexed into a ds3 signal. ? allows the m12 stages to be bypassed allowing direct input of ds2 signals into the m23 multiplexer stage. provides a generic microprocessor interface for configuration, control, and status monitoring. low power cmos technology. packaged in a 208 pin plastic quad flat pack (pqfp) package. each ds3 framer/performance monitor section: frames to a ds3 signal with a maximum average reframe time of less than 1.5 ms (as required by tr-tsy-000009 section 4.1.2 and tr-tsy-000191 section 5.2). decodes a b3zs-encoded signal and indicates line code violations. the definition of line code violation is software selectable. detects and accumulates occurrences of excessive zeros and loss of signal. provides indication of m-frame and m-subframe boundaries, and overhead bit positions in the ds3 stream. detects the ds3 alarm indication signal (ais) and idle signal. detection algorithms operate correctly in the presence of a 10 -3 bit error rate. extracts valid x-bits and indicates far end receive failure. accumulates up to 65,535 line code violation (lcv) events per second, 16,383 p-bit parity error events per second, 1023 f-bit or m-bit (framing bit) events per second, 65,535 excessive zero (exz) events per second, and when enabled for c-bit
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 2 parity mode operation, up to 16,383 c-bit parity error events per second, and 16,383 far end block error (febe) events per second. detects and validates bit-oriented codes in the c-bit parity far end alarm and control channel. terminates the c-bit parity path maintenance data link with an integral hdlc receiver having a 4-byte deep fifo buffer. supports polled, interrupt-driven or dma access. optionally extracts the c-bit parity mode path maintenance data link signal and serializes it at 28.2 kbit/s. extracts the x, p, m, f, c and stuff opportunity bits and serializes them at 526 kbit/s on a time division multiplex signal. each ds3 transmit framer section: provides the overhead bit insertion for a ds3 stream. provides a bit serial clock and data interface, and allows the m-frame boundary and/or the overhead bit positions to be located via an external interface provides optional insertion of the x, p, m, f, c, and stuff opportunity bits via a 526 kbit/s serial interface. provides b3zs encoding. inserts far end receive failure (ferf), the ds3 alarm indication signal (ais) and the idle signal when enabled by external inputs, or internal register bits. provides diagnostic features to allow the generation of line code violation error events, parity error events, framing bit error events, and when enabled for the c-bit parity application, c-bit parity error events, and far end block error events. inserts bit-oriented codes in the c-bit parity far end alarm and control channel. optionally inserts the c-bit parity path maintenance data link with an integral hdlc transmitter. supports polled, interrupt-driven, or dma access.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 3 optionally inserts the c-bit parity mode path maintenance data link signal from a 28.2 kbit/s serial input. each m23 multiplexer section: multiplexes 7 ds2 bit streams into a single m23 format ds3 bit stream. performs required bit stuffing including generation of c-bits. includes required fifo buffers for rate adaptation in the multiplex path. allows insertion of per ds2 payload loopback requests encoded in the transmitted c-bits to be activated or cleared under microprocessor control. provides generated ds2 clock for use in integrated m13 or c-bit parity multiplex applications. demultiplexes a single m23 format ds3 bit stream into 7 ds2 bit streams. performs required bit destuffing including interpretation of c-bits. detects per ds2 payload loopback requests encoded in the received c-bits. allows per ds2 payload loopback to be activated or cleared under microprocessor control. allows per ds2 alarm indication signal (ais) to be activated or cleared for either direction under microprocessor control. allows ds2 alarm indication signal (ais) to be activated or cleared in the demultiplex direction automatically upon loss of ds3 frame alignment or signal. supports c-bit parity ds3 format. each ds2 framer and m12 multiplexer section: supports two asynchronous multiplexing standards: the combination of four ds1 bit streams into a single m12 format ds2 bit stream and the combination of three 2048 kbit/s tributaries into a 6312 kbit/s high speed signal according to ccitt recommendation g.747. frames to either a ds2 or g.747 signal.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 4 maximum average reframe time of less than 7 ms (as required by tr-tsy- 000009 section 4.1.2 and tr-tsy-000191 section 5.2) for ds2 format and 1 ms for g.747 format. allows forcing of reframe via an internal register. detects the alarm indication signal in 9.9 ms in the presence of a 10 -3 bit error rate. extracts the ds2 x-bit or g.747 remote alarm bit and indicates far end receive failure. accumulates error events over consecutive accumulation intervals as defined by writes to internal registers. accumulates up to 255 ds2 m-bit or f-bit error events per second. accumulates up to 255 g.747 framing bit or word (selectable) error events per second. accumulates up to 8191 g.747 parity error events per second. optionally generates interrupts when various events or status changes occur. performs required bit stuffing including generation of c-bits. performs required bit destuffing including interpretation of c-bits. includes required fifo buffers for rate adaptation in the multiplex path. allows per tributary alarm indication signal (ais) to be activated or cleared for either direction under microprocessor control. ds2 functionality multiplexes four ds1 bit streams into a single m12 format ds2 bit stream. performs required inversion of second and fourth multiplexed ds1 streams as required by ansi t1.107 section 7.2. allows insertion of per ds1 payload loopback requests encoded in the transmitted c-bits to be activated or cleared under microprocessor control. inserts x, f, and m bits into transmitted ds2 bit stream.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 5 allows transmission of far end receive failure (ferf) and alarm indication signal (ais) under microprocessor control. allows inversion of inserted f or m bits for diagnostic purposes. demultiplexes a single m12 format ds2 bit stream into four ds1 bit streams. detects per ds1 payload loopback requests encoded in the received c-bits. allows per ds1 payload loopback to be activated or cleared under microprocessor control. performs required inversion of second and fourth demultiplexed ds1 streams. e1 functionality multiplexes three 2048 kbit/s bit streams into a single g.747 format 6312 kbit/s bit stream. inserts frame alignment signal and parity bit into transmitted 6312 kbit/s bit stream. allows transmission of remote alarm indication (rai) and reserved bit (set ii, bit 3) under microprocessor control. allows inversion of inserted frame alignment signal for diagnostic purposes. allows inversion of the c-bits in anticipation of remote loopback recommendations. demultiplexes a single g.747 format 6312 kbit/s bit stream into three 2048 kbit/s bit streams.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 6 2 applications m23 based m13 multiplexer c-bit parity based m13 multiplexer m23 multiplexer m13 multiplexer supporting g.747 tributary format
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 7 3 standard references 1. american national standard for telecommunications, ansi t1.103-1987 - "digital hierarchy - synchronous ds3 format specifications". 2. american national standard for telecommunications, ansi t1.107-1988 - "digital hierarchy - formats specifications". 3. american national standard for telecommunications, ansi t1.404-1989 - "customer installation-to-network - ds3 metallic interface specification". 4. american national standard for telecommunications, ansi t1.107a-1990 - "digital hierarchy - supplement to formats specifications (ds3 format applications)". 5. american national standard for telecommunications, t1m1.3/91-003r3 - "in- service digital transmission performance monitoring draft standard". 6. bell communications research, tr-tsy-000009 - "asynchronous digital multiplexes requirements and objectives," issue 1, may 1986. 7. bell communications research, tr-tsy-000191 - "alarm indication signal requirements and objectives," issue 1, may 1986. 8. bell communications research, tr-tsy-000233 - "wideband and broadband digital cross-connect systems generic requirements and objectives," issue 2, september 1990. 9. bell communications research, tr-tsy-000820 - "otgr: network maintenance transport surveillance - generic digital transmission surveillance, section 5.1," issue 1, june 1990. 10. bell communications research, tr-nwt-000499 - "transport systems generic requirements (tsgr) - common requirements," issue 4, november 1991. 11. ccitt blue book, recommendation q.921 - "isdn user-network interface data link layer specification", volume vi, fascicle vi.10, 1988. 12. ccitt blue book, recommendation g.747 - "second order digital multiplex equipment operating at 6312 kbit/s and multiplexing three tributaries at 2048 kbit/s", volume iii, fascicle iii.4, 1988.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 8 13. international organization for standardization, iso 3309:1984 - "high-level data link control procedures -- frame structure".
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 9 4 application example figure 1 - m1-3 multiplexer/demultiplexer lin+ nc-r lin- rgnd rfo tgnd lout+ nc-t lout- rpos rneg rclk lf1 lf2 tpos tneg tclk ss i 7 8 p 72 0 0 ds- 3 l ine in ter fac e rpos rneg rclk tpos tneg tclk ticlk toh tohen timfp tohclk tohfp a[7:0] d[7:0] ale rdb wrb csb rstb rd1dat1 rd1clk1 td1dat1 td1clk1 rd1dat2 rd1clk2 td1dat2 td1clk2 rd1dat3 rd1clk3 td1dat3 td1clk3 rd1dat4 rd1clk4 td1dat4 td1clk4 ? ? ? ? ? rd1dat28 rd1clk28 td1dat28 td1clk28 in tb pm8 31 3 d3 mx ad[15:0] ale rdb wrb resb int p from master reset circuitry from chip select decode circuitry +5v tdd[1] tclki[1] rdd[1] rclko[1] tdd[2] tclki[2] rdd[2] rclko[2] tdd[3] tclki[3] rdd[3] rclko[3] tdd[4] tclki[4] rdd[4] rclko[4] a[8:0] d[7:0] ale rdb wrb csb rstb pm 43 1 4 qd s x (7 quad dsx-1/e1 line interfaces) txtip[1] txring[1] rxtip[1] rxring[1] txtip[2] txring[2] rxtip[2] rxring[2] txtip[3] txring[3] rxtip[3] rxring[3] txtip[4] txring[4] rxtip[4] rxring[4] in tb from/to p 1:2 1:1.36 ? ? ? ? ? ? ? ? ? 1:2 1:1.36 note: use of the ssi liu as illustrated requires that ticlk has a duty cycle of 45% min 55% max or better (e.g. using a connor winfield s65t3 reference oscillator).
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 10 5 block diagram roclk, rodat, rmfp, rmsfp, rohp, rohclk, rohfp, roh, rlos, rexz, rais, roof/rred, rferf rdlclk/rdlint rdlsig/rdleom rclk/vclk rneg/rlcv rpos/rdat tneg/tmfp tdlsig/tdludr tdlclk/td lint ticlk timfp toh tohfp tdleomi tohen tohclk gd2clk td2clk d[7:0] a[7:0] ale csb rdb wrb rstb intb microprocessor i/f rx o/h access tran ds3 transmit framer frmr ds3 receive framer tpos/tdat b3zs encode b3zs decode tclk xfdl tx hdlc xboc tx feac rfdl rx hdlc rboc rx feac pmon perf. monitor mx23 m23 mux/demux ds2 frmr framer mx12 m12 mux/ demux #1 #2-#7 td1clk4 td1dat4 td1clk[3:1] td1dat[3:1] rd1clk[3:1] rd1dat[3:1] rd1clk4 rd1dat4 td1clk[28:5] td1dat[28:5] rd1clk[28:5] rd1dat[28:5] remaining six m12 tx o/h access one of seven m12 a8/trs
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 11 description the pm8313 d3mx m13 multiplexer supports asynchronous multiplexing and demultiplexing of 28 ds1s, 21 e1s or 7 ds2s into a ds3 signal. the device supports ansi t1.107, bell communications research tr-tsy-000009 and ccitt recommendation g.747 standards. receive ds3 framing is provided by the ds3 frmr framer block. the frmr accepts either a b3zs encoded bipolar, or a unipolar signal compatible with m23 and c-bit parity applications. the frmr frames to a ds3 signal with a maximum average reframe time of 1.5 ms in the presence of a 10 -3 bit error rate. the frmr indicates line code violations, loss of signal, framing bit errors, parity errors, c-bit parity errors, and far end block errors (febe). the frmr detects far end receive failure (x-bits set to 0), the alarm indication signal (ais), and the idle signal. the frmr is an off-line framer, indicating both out of frame (oof) and change of frame alignment (cofa) events. the error events (fer, cbit parity error, febe, etc.) are still indicated while the framer is oof, based on the previous frame alignment. the c-bit parity far end alarm channel (feac) and path maintenance data link are supported. bit oriented codes in the feac channel are detected by the rboc bit-oriented code receiver block. if enabled, the rboc generates an interrupt when a valid code has been received. the path maintenance data link is terminated using either the rfdl data link receiver block or an external hdlc receiver. the rfdl supports polled, interrupt driven, and dma servicing. ds3 error event accumulation is provided by the ds3 pmon performance monitor block. the pmon accumulates framing bit errors, line code violations, excessive zeros occurrences, parity errors, c-bit parity errors, and far end block errors. error accumulation continues even while the off-line framer is indicating oof. the counters are intended to be polled once per second, and are sized so as not to saturate at a 10 -3 bit error rate. transfer of count values to holding registers is initiated through the microprocessor interface. ds3 transmit framing insertion is provided by the ds3 tran transmitter block. it outputs either a b3zs encoded bipolar signal, or a unipolar signal. the ds3 tran inserts the x, p, m, c, and f bits into the outgoing ds3 stream. the ds3 tran block inserts far end receive failure, ais, and the idle signal under the control of external inputs, or internal register bits. diagnostic features are provided to allow the generation of line code violation error events, parity error events, framing bit error events, and when enabled for the c-bit parity application, c-bit parity error events, and far end block error events. external
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 12 inputs allow substitution of the overhead bits or the sourcing of ais, idle signal or far end receive failure indication. when configured for the c-bit parity application, bit oriented codes in the feac channel are inserted by the xboc bit-oriented code transmitter block. the feac code is controlled by an internal register. the path maintenance data link is inserted using the xfdl data link transmitter block or an external hdlc transmitter. the xfdl supports polled, interrupt driven, and dma servicing. the demultiplexing and multiplexing of seven 6312 kbit/s data streams into and out of the ds3 is performed by the mx23 m23 multiplexer block. the mx23 contains fifos and performs bit stuffing for the rate adaptation of the ds2s. the c-bits are set appropriately, with the option of inserting ds2 loopback requests. the mx23 may be configured to generate an interrupt upon the detection of loopback requests in the received ds3. ais may be inserted in the any of the 6312 kbit/s tributaries in both directions. c-bit parity is supported by sourcing a 6.3062723 mhz clock, which corresponds to a stuffing ratio of 100%. framing to the demultiplexed 6312 kbit/s data streams is provided by the ds2 frmr framer. it supports both ds2 (ansi ti.107) and ccitt recommendation g.747 frame formats. the maximum average reframe time is 7 ms for ds2 and 1ms for g.747. in ds2 mode, it detects far end receive failure and accumulates m-bit and f-bit errors. in g.747 mode, it detects remote alarm and accumulates framing word errors and parity errors. the ds2 frmr is an off-line framer, indication both oof and cofa events. error events (ferf, merr, ferr, perr, rai, framing word errors) are still indicated while the ds2 framer is indicating oof, based on the previous alignment. the multiplexing and demultiplexing of the low speed tributaries into and out of a 6312 kbit/s data stream is performed by seven mx12 m12 multiplexers. each of the mx12 blocks may be independently configured to multiplex and demultiplex four 1544 kbit/s ds1s into and out of a ds2 formatted signal or to multiplex and demultiplex three 2048 kbit/s signals into and out of a g.747 formatted signal. each mx12 may be independently bypassed so an external ds2 may by multiplexed and demultiplexed directly into and out of the ds3. the mx12 contains fifos and performs bit stuffing to accommodate the tributary frequency deviations. the c-bits are set appropriately, with the option of inserting ds1 loopback requests. the mx12 block may be configured to generate an interrupt upon the detection of loopback requests in the received ds2. ais may be inserted in any of the low speed tributaries in both directions.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 13 6 pin diagram the d3mx is packaged in a 208 pin pqfp package having a body size of 28 mm by 28 mm and a pin pitch of 0.5 mm. pm8313 d3mx rd1clk6 td1dat7 rd1dat7 td1clk7 rd1clk7 nc vddo vsso td1dat8 rd1dat8 td1clk8 rd1clk8 td1dat9 d0 d1 vsso d2 d3 d4 d5 nc td1dat4 vsso rd1dat4 td1clk4 rd1clk4 td1dat5 td1clk2 rd1clk2 timfp tdlclk/tdling td2clk tdlsig/tdludr tdleomi td1dat1 rd1dat1 td1clk1 vsso vddo rd1clk1 nc td1dat2 rd1dat9 td1clk9 rd1clk9 td1dat10 rd1dat10 td1clk10 rd1clk10 td1dat11 rd1dat11 td1clk11 nc td1clk15 ticlk tclk tpos/tdat rais tneg/tmfp gd2clk rodat vsso vddo roclk rmfp nc tohclk tohfp vsso nc rd1clk27 td1dat28 rd1dat28 td1clk28 rd1clk28 nc vddi vssi rstb a8 a7 a6 rd1dat2 nc vssi td1dat3 rd1clk11 rmsfp toh tohen rohfp td1clk27 rd1dat27 td1dat27 td1dat12 rd1dat12 td1clk12 rdb wrb vddi rd1dat3 td1clk3 rd1clk3 roh rohclk rlos rferf roof/rred rd1clk26 rd1clk12 td1dat13 nc rd1dat13 td1clk13 td1clk26 nc rd1dat26 td1dat26 rexz rclk/vclk vsso rpos/rdat rneg/rlcv rdlclk/rdlint rdlsig/rdleom rd1clk13 rd1clk25 td1clk25 rd1dat25 nc td1dat25 rd1clk24 td1clk24 rd1dat24 td1dat14 rd1dat14 td1clk14 rd1clk14 vsso td1dat15 rd1dat15 nc rd1dat5 td1clk5 rd1clk5 td1dat6 rd1dat6 td1clk6 nc intb td1dat20 rd1clk15 td1dat16 rd1dat16 td1clk16 rd1clk16 vddo td1dat17 nc td1dat24 rd1clk23 td1clk23 rd1dat23 td1dat23 rd1clk22 td1clk22 d6 vddo d7 csb ale a0 a1 a2 a3 a4 a5 nc rd1dat22 vddo vsso td1dat22 rd1clk21 td1clk21 rd1dat21 td1dat21 rd1clk20 td1clk20 rd1dat20 rd1dat17 td1clk17 rd1clk17 td1dat18 rd1dat18 td1clk18 vsso rd1clk18 td1dat19 rd1dat19 td1clk19 rd1clk19 pin 1 pin 208 pin 157 pin 156 pin 52 pin 53 pin 104 index pin 105 rohp nc nc nc nc nc nc
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 14 7 pin description pin name type pin no. function rclk/ vclk input 26 the receive input clock (rclk) provides timing for the receive side of the d3mx. rclk is nominally a 44.736 mhz, 50% duty cycle clock. the test vector clock (vclk) signal is used during d3mx production testing to verify internal functionality. rpos/ rdat input 29 the positive input pulse (rpos) signal represents the positive pulses received on the b3zs-encoded line when configured for dual rail reception. the receive data input (rdat) signal represents the unipolar ds3 input stream when configured for single rail operation. both rpos and rdat are sampled on the rising edge of rclk by default and may be enabled to be sampled on the falling edge of rclk. rneg/ rlcv input 30 the negative input pulse (rneg) signal represents the negative pulses received on the b3zs-encoded line when configured for dual rail reception. line code violations (lcvs) may be input on the receive line code violation (rlcv) signal when configured for single rail operation. both rneg and rlcv are sampled on the rising edge of rclk by default and may be enabled to be sampled on the falling edge of rclk. roclk output 10 the receive output clock (roclk) signal provides timing for downstream processing. roclk is nominally a 44.736 mhz, 50% duty cycle clock. rodat, rmfp, rmsfp, rlos, rexz and rohp are updated on the falling edge of roclk. roclk is a buffered version of rclk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 15 pin name type pin no. function rodat output 7 the receive data output (rodat) signal carries the 44.736 mbit/s nrz stream decoded from the b3zs line signal. the frame alignment signals (rmfp, rmsfp, and rohp) are aligned to the rodat stream. rodat is updated on the falling edge of roclk. rmfp output 11 the receive m-frame pulse (rmfp) signal marks the first bit (x1) in the m-frame of the ds3 signal on rodat. when the framer is out- of-frame, rmfp continues to operate with timing aligned to the old m-frame position. when the framer regains frame alignment the rmfp timing is updated, which may result in a change of frame alignment. rmfp is updated on the falling edge of roclk. rmsfp output 16 the receive m-subframe pulse (rsmfp) signal marks the first bit (x, p, and m) in each m- subframe of the received ds3 stream (rodat) when the framer is in-frame. when the framer is out-of-frame, rsmfp continues to operate with timing aligned to the old m-frame position. when the framer regains frame alignment the rmsfp timing is updated, which may result in a change of frame alignment. rsmfp is updated on the falling edge of roclk. rohp output 12 the receive overhead pulse (rohp) signal marks the overhead bit positions (x, p, m, c, and f) in the received ds3 stream (rodat) when the framer is in-frame. when the framer is out-of-frame, rohp continues to operate with timing aligned to the old m-frame position. when the framer regains frame alignment the rohp timing is updated, which may result in a change of frame alignment. rohp is updated on the falling edge of roclk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 16 pin name type pin no. function rohclk output 21 the receive overhead clock (rohclk) cycles once per overhead bit. rohclk is nominally a 526 khz clock. roof, rferf, rais, ridl, rferr, roh, and rohfp are updated on the falling edge of rohclk. roh output 20 the receive overhead data (roh) signal contains the overhead bits (c, f, x, p, and m) extracted from the received ds3 stream. roh is updated on the falling edge of rohclk. rohfp output 19 the receive overhead frame position (rohfp) signal may be used to locate the individual overhead bits in the received overhead data stream, roh. rohfp is high during the x1 overhead bit position in the roh stream. rohfp is updated on the falling edge of rohclk. rlos output 22 the receive loss of signal (rlos) status is set high when the dual rail nrz format stream is selected, and 175 successive zeros are detected on the rpos and rneg inputs. rlos is set low when the ones' density is greater than 33% for 175 1 bit periods on the rpos and rneg inputs. rlos is updated on the falling edge of roclk. rexz output 25 the receive excessive zero (rexz) signal indicates the presence of 3 or more consecutive zeros in the received ds3 bipolar stream. rexz pulses high for one roclk cycle whenever 3 or more consecutive zeros are detected. when the receive ds3 interface is configured to for uni-polar data, the rexz output is forced low. rexz is updated on the falling edge of roclk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 17 pin name type pin no. function rais output 4 the receive alarm indication signal (rais) indicates the presence of ais in the received ds3 stream. rais is set high when the ais pattern has been received for 2.23 ms or 13.5 ms (software selectable). rais is set low when the ais pattern has not been received for 2.23 ms or 13.5 ms. rais is updated on the falling edge of rohclk. roof/ output 24 the receive out-of-frame (roof) signal is set high when an out-of-frame condition is declared. an out-of-frame is declared when 3 out of 16 (default) or 3 out of 8 consecutive f- bit errors are detected, or when one or more m- bit errors is detected in 3 out of 4 consecutive m-frames. roof is set low when an in-frame condition is declared. roof is updated on the falling edge of rohclk. this roof signal is available when the redo bit in the master alarm enable register is logic 0. rred the receive red alarm (rred) signal is available when the redo bit in the master alarm enable register is logic 1. the rred output is set high when a ds3 out-of-frame condition or ds3 loss of signal condition has been present for either 2.23ms or 13.5 ms. the rred output is set low when a ds3 out-of- frame condition or ds3 loss of signal condition has been absent for either 2.23ms or 13.5 ms. rred is updated on the falling edge of rohclk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 18 pin name type pin no. function rferf output 23 the receive far end receive failure (rferf) signal reflects the value of the internal ferf state buffered by two m-frames. internally, ferf is set high when both x-bits (x1 and x2) are received as logic 0 in the current m-frame; ferf is set low when both x-bits are received as logic 1. ferf remains in its previous state when x1 ? x2 in the current m-frame. the rferf output latency provides a better than 99.99% chance of freezing (i.e. holding rferf in its previous state) upon a valid state value during the occurrence of an out of frame. rferf is updated once per m-frame on the falling edge of rohclk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 19 pin name type pin no. function rdlclk/ rdlint output 31 the receive data link clock (rdlclk) signal is active when an external hdlc receiver is selected (the rexhdlc bit in the master hdlc configuration register is a logic 1). the rdlclk signal provides timing for the external processing of the path maintenance data link signal extracted by the ds3 frmr. rdlclk is updated on the falling edge of the rohclk signal and cycles 3 times per m-frame. rdlclk is nominally a 28.2 khz clock, which is low for at least 1.9 s per cycle. the data link interrupt (rdlint) signals is active when the internal hdlc receiver is selected (the rexhdlc in the master hdlc configuration register bit is a logic 0). the rdlint signal is asserted when an event occurs which changes the status of the hdlc receiver. rdlint is updated on the falling edge of the rohclk signal. rdlint is deasserted when the interrupt enable/status register is read in the hdlc receiver. by default rdlint is an active low open-drain output, but can be configured as active high. typically, rdlint would be connected to an external dma device. if the supervising microprocessor is desired to service the rfdl, this output can be wired-ored with the intb output when rdlint is configured as an active-low open drain output.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 20 pin name type pin no. function rdlsig/ rdleom output 32 the receive data link (rdlsig) signal is active when an external hdlc receiver is selected (the rexhdlc bit in the corresponding master hdlc configuration register is a logic 1). the rdlsig signal carries bits extracted from the three c-bits in m-subframe #5 by the ds3 framer. rdlsig is held high when c-bit parity mode is not enabled. rdlsig is updated on the falling edge of the corresponding rdlclk signal. the receive end of message (rdleom) signal is active if the internal hdlc receiver is selected (the rexhdlc bit in the master hdlc configuration register is a logic 0). the rdleom signal is asserted when the last byte of a sequence is read from the hdlc receiver, or if the receiver's buffer overruns. rdleom is updated on the falling edge of the rohclk signal. rdleom is deasserted when the interrupt enable/status register is read in the hdlc receiver. by default, rdleom is an active low open-drain output, but can be configured as active high. typically, rdleom would be connected to the supervising microprocessor when an external dma is used, signaling the microprocessor that a complete message is ready. in this case the rdleom is configured as an active-low open drain output and wired-ored with the intb output.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 21 pin name type pin no. function rd1clk1 rd1clk2 rd1clk3 rd1clk4 rd1clk5 rd1clk6 rd1clk7 rd1clk8 rd1clk9 rd1clk10 rd1clk11 rd1clk12 rd1clk13 rd1clk14 rd1clk15 rd1clk16 rd1clk17 rd1clk18 rd1clk19 rd1clk20 rd1clk21 rd1clk22 rd1clk23 rd1clk24 rd1clk25 rd1clk26 rd1clk27 rd1clk28 output 198 193 186 180 175 170 166 159 155 151 146 142 137 133 127 122 116 110 106 102 98 91 87 82 76 71 66 62 the receive ds1 clock (rd1clk[28:1]) signals provide timing for each of the 28 demultiplexed ds1 streams. the rd1clk[28:1] signals are nominally 1.544 mhz clocks, but have substantial jitter due to the demultiplexing and destuffing processes. the rd1dat[28:1] outputs are updated on the falling edges of the corresponding rd1clk[28:1] signals. when the internal m12 multiplexers are configured for g.747 multiplexing, every fourth rd1clk signal (rd1clk4, 8, 12, 16, 20, 24, 28) is unused and held low. the remaining rd1clk signals are then nominally 2.048 mhz clocks. when the internal m12 multiplexers are bypassed, every fourth rd1clk signal (rd1clk4, 8, 12, 16, 20, 24, 28) may become a ds2 rate clock operating at nominally 6.312 mhz. the remaining rd1clk signals for the particular m12 multiplexer bypassed are then unused and held low. the internal m12 multiplexers may be bypassed or configured for g.747 multiplexing on an individual basis. thus the configuration of each of the seven blocks of four rd1clk signals is independently programmable.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 22 pin name type pin no. function rd1dat1 rd1dat2 rd1dat3 rd1dat4 rd1dat5 rd1dat6 rd1dat7 rd1dat8 rd1dat9 rd1dat10 rd1dat11 rd1dat12 rd1dat13 rd1dat14 rd1dat15 rd1dat16 rd1dat17 rd1dat18 rd1dat19 rd1dat20 rd1dat21 rd1dat22 rd1dat23 rd1dat24 rd1dat25 rd1dat26 rd1dat27 rd1dat28 output 202 195 188 182 177 173 168 161 157 153 149 144 139 135 129 124 118 114 108 104 100 94 89 84 78 74 69 64 the receive ds1 data (rd1dat[28:1]) signals carry the 28 demultiplexed ds1 streams. the rd1dat[28:1] outputs are updated on the falling edges of the corresponding rd1clk[28:1] signals. when the internal m12 multiplexers are configured for g.747 multiplexing, every fourth rd1dat signal (rd1dat4, 8, 12, 16, 20, 24, 28) is unused and held low. the remaining rd1dat signals are then nominally 2.048 mbit/s data streams. when the internal m12 multiplexers are bypassed, every fourth rd1dat signal (rd1dat4, 8, 12, 16, 20, 24, 28) may become a ds2 rate data stream operating at nominally 6.312 mbit/s. the remaining rd1dat signals for the particular m12 multiplexer bypassed are then unused and held low. the internal m12 multiplexers may be bypassed or configured for g.747 multiplexing on an individual basis. thus the configuration of each of the seven blocks of four rd1dat signals is independently programmable.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 23 pin name type pin no. function td1clk1 td1clk2 td1clk3 td1clk4 td1clk5 td1clk6 td1clk7 td1clk8 td1clk9 td1clk10 td1clk11 td1clk12 td1clk13 td1clk14 td1clk15 td1clk16 td1clk17 td1clk18 td1clk19 td1clk20 td1clk21 td1clk22 td1clk23 td1clk24 td1clk25 td1clk26 td1clk27 td1clk28 input 201 194 187 181 176 172 167 160 156 152 148 143 138 134 128 123 117 112 107 103 99 92 88 83 77 72 68 63 the transmit ds1 clock (td1clk[28:1]) signals provide timing for each of the 28 ds1 streams to be multiplexed. the td1clk[28:1] signals should nominally be 1.544 mhz clocks, and should have the minimal jitter and wander of a standard ds1 line signal. the td1dat[28:1] inputs are sampled on the rising edges of the corresponding td1clk[28:1] signals. when the internal m12 multiplexers are configured for g.747 multiplexing, every fourth td1clk signal (td1clk4, 8, 12, 16, 20, 24, 28) is unused and ignored. the remaining td1clk signals should then nominally be 2.048 mhz clocks. when the internal m12 multiplexers are bypassed, every fourth td1clk signal (td1clk4, 8, 12, 16, 20, 24, 28) should then become a ds2 rate clock operating at nominally 6.312 mhz. the remaining td1clk signals for the particular m12 multiplexer bypassed are then unused and ignored. the internal m12 multiplexers may be bypassed or configured for g.747 multiplexing on an individual basis. thus the configuration of each of the seven blocks of four td1clk signals is independently programmable.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 24 pin name type pin no. function td1dat1 td1dat2 td1dat3 td1dat4 td1dat5 td1dat6 td1dat7 td1dat8 td1dat9 td1dat10 td1dat11 td1dat12 td1dat13 td1dat14 td1dat15 td1dat16 td1dat17 td1dat18 td1dat19 td1dat20 td1dat21 td1dat22 td1dat23 td1dat24 td1dat25 td1dat26 td1dat27 td1dat28 input 203 196 190 184 179 174 169 162 158 154 150 145 141 136 130 126 120 115 109 105 101 97 90 86 81 75 70 65 the transmit ds1 data (td1dat[28:1]) signals carry the 28 ds1 streams to be multiplexed. the td1dat[28:1] inputs are sampled on the rising edges of the corresponding td1clk[28:1] signals. when the internal m12 multiplexers are configured for g.747 multiplexing, every fourth td1dat signal (td1dat4, 8, 12, 16, 20, 24, 28) is unused and ignored. the remaining td1dat signals should then nominally be 2.048 mbit/s data streams. when the internal m12 multiplexers are bypassed, every fourth td1dat signal (td1dat4, 8, 12, 16, 20, 24, 28) may become a ds2 rate data stream operating at nominally 6.312 mbit/s. the remaining td1dat signals for the particular m12 multiplexer bypassed are then unused and ignored. the internal m12 multiplexers may be bypassed or configured for g.747 multiplexing on an individual basis. thus the configuration of each of the seven blocks of four td1dat signals is independently programmable.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 25 pin name type pin no. function gd2clk output 6 the transmit generated ds2 clock (gd2clk) signal is provided for use in integrated m13 or c-bit parity multiplex applications. when configured for m13 operation, gd2clk is nominally a 6.311993 mhz clock, which corresponds to a stuffing ratio of 39.1%. when configured for c-bit parity operation, gd2clk is nominally a 6.3062723 mhz clock, which corresponds to a stuffing ratio of 100%. the gd2clk may be connected to the td2clk input clock. gd2clk is updated on the falling edge of tclk. td2clk input 206 the transmit ds2 clock (td2clk) signal provides timing for the multiplex side of all of the mx12 tsbs. td2clk is nominally a 6.312 mhz, 50% duty cycle clock.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 26 pin name type pin no. function tdlsig/ tdludr i/o 205 the transmit data link (tdlsig) signal is active when an external hdlc receiver is selected (the texhdlc bit in the corresponding master hdlc configuration register is a logic 1). the tdlsig signal carries bits to be inserted in the three c-bits in m-subframe #5 by the ds3 transmitter. tdlsig is ignored when c-bit parity mode is not enabled. tdlsig is sampled on the rising edge of the tdlclk signal. the transmit data link underrun (tdludr) signal is active when the internal hdlc receiver is selected (the texhdlc bit in the corresponding master hdlc configuration register is a logic 0). tdludr is asserted when the internal hdlc transmitter underruns. tdludr is deasserted by writing to the xfdl interrupt status register. by default tdludr is an active low open-drain output, but can be configured as active high. upon a reset, the texhdlc bit a logic 1, thus, the pin is configured as an input, tdlsig. typically, tdludr would be connected to the supervising microprocessor when an external dma is used, signaling the microprocessor that a severe error has occurred causing the transmit buffer to underrun. in this case the tdludr is configured as an active-low open drain output and wired-ored with the intb output.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 27 pin name type pin no. function tdlclk/ tdlint output 207 the transmit data link clock (tdlclk) signal is active when an external hdlc receiver is selected (the texhdlc bit in the master hdlc configuration register is a logic 1). the tdlclk signal provides timing for the external sourcing of the path maintenance data link signal inserted by the ds3 tran. tdlclk is updated on the falling edge of the tohclk signal and cycles 3 times per m-frame. tdlclk is nominally a 28.2 khz clock, which is low for at least 1.9 s per cycle. the transmit data link interrupt (tdlint) signal is active when the internal hdlc transmitter is selected (the texhdlc bit in the corresponding master hdlc configuration register is a logic 0).tdlint is asserted when the last data byte written to the internal hdlc transmitter has been setup for transmission, and a write is required to the xfdl configuration register, or the xfdl transmit data register to either end the current message transmission, or to provide more data. by default tdlint is an active low open- drain output, but can be configured as active high. typically, tdlint would be connected to an external dma device. if the supervising microprocessor is desired to service the xfdl, this output can be wired-ored with the intb output when tdlint is configured as an active- low open drain output.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 28 pin name type pin no. function tdleomi input 204 the transmit data link end of message input (tdleomi) provides a method for an external dma controller to signal the end of the transmitted message to the hdlc transmitter without needing to write to the xfdl configuration register. the tdleomi input is active high and must be glitch-free. it internally sets the corresponding eom register bit in the xfdl configuration register. the tdleomi input may be asserted during or after the write of the last byte of a packet but before the next byte would be expected (within 210 s of the last assertion of tdlint or the int bit in the xfdl status register). tdleomi must be deasserted before the write of the first byte of the next packet. tdleomi is ignored if no data transmission is pending. ticlk input 1 the transmit input clock (ticlk) provides the transmit direction timing. ticlk is nominally a 44.736 mhz, 50% duty cycle clock. timfp is sampled on the rising edge of ticlk. timfp input 208 the transmit m-frame pulse input (timfp) signal allows one to control the alignment of the m-frame of the transmitted ds3 stream (tdat). the first bit (x1) of the m-frame on tdat will occur within several ticlk cycles and be identified by the tmfp output signal. timfp may be tied low if such control is not required. timfp is sampled on the rising edge of ticlk. toh input 17 the transmit overhead data (toh) signal contains the overhead bits (c, f, x, p, and m) that may be inserted in the transmitted ds3 stream. toh is sampled on the rising edge of tohclk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 29 pin name type pin no. function tohen input 18 the transmit overhead insertion (tohen) signal controls the insertion of ds3 overhead bits from the toh input. when tohen is high, the associated overhead bit in the toh stream is inserted in the transmitted ds3 frame. when tohen is low, the ds3 overhead bit is generated and inserted internally. tohen is sampled on the rising edge of tohclk. tohfp output 15 the transmit overhead frame position (tohfp) signal may be used to align the individual overhead bits in the transmitted overhead data stream, toh, to the ds3 m-frame. tohfp is high during the x1 overhead bit position in the toh stream. tohfp is updated on the falling edge of tohclk. tohclk output 14 the transmit overhead clock (tohclk) cycles once per overhead bit. tohclk is nominally a 526 khz clock. tohfp is updated on the falling edge of tohclk. toh, and tohen are sampled on the rising edge of tohclk. tclk output 2 the transmit clock (tclk) provides timing for circuitry downstream of the ds3 transmitter of the d3mx. tclk is nominally a 44.736 mhz, 50% duty cycle clock. tpos/ tdat output 3 the transmit positive pulse (tpos) signal represents the positive pulses transmitted on the b3zs-encoded line when configured for dual-rail operation. tpos is updated on the falling edge of tclk by default but may be enabled to be updated on the rising edge of tclk. the transmit data output (tdat) signal represents a unipolar ds3 output stream when configured for single rail operation. tdat is updated on the falling edge of tclk by default but may be enabled to be updated on the rising edge of tclk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 30 pin name type pin no. function tneg/ tmfp output 5 the transmit negative pulse (tneg) signal represents the negative pulses transmitted on the b3zs-encoded line when configured for dual rail operation. tneg is updated on the falling edge of tclk by default but may be enabled to be updated on the rising edge of tclk. the transmit multiframe pulse (tmfp) signal marks the transmit m-frame alignment when configured for single rail operation. the tmfp output is high during the first bit (x1) of the ds3 multiframe presented on tdat. tmfp is updated on the falling edge of tclk by default but may be enabled to be updated on the rising edge of tclk. intb output 33 the active low interrupt (intb) signal goes low when one of the ds3 frmr, rboc, ds2 frmr, mx12, mx23 or pmon tsbs generates an interrupt, provided that the interrupt source in question is not masked. intb goes high when the interrupt enable/status register is read in the corresponding tsb. note that intb will remain low until all active, unmasked interrupt sources are acknowledged. the intb signal is an open drain output. csb input 45 the active low chip select (csb) signal is low during d3mx register accesses. csb must go high at least once after a powerup to clear internal test modes. if csb is not used, then it should be tied to an inverted version of rstb, in which case rdb and wrb determine register accesses rdb input 57 the active low read enable (rdb) signal is low during d3mx register read accesses. the d3mx drives the d7-d0 bus with the contents of the addressed register while rdb and csb are low.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 31 pin name type pin no. function wrb input 56 the active low write strobe (wrb) signal is low during a d3mx register write access. the d7- d0 bus contents are clocked into the addressed register on the rising wrb edge while csb is low. d0 d1 d2 d3 d4 d5 d6 d7 i/o 34 35 37 38 39 41 42 44 the bidirectional data bus (d7-d0) is used during d3mx register read and write accesses. a0 a1 a2 a3 a4 a5 a6 a7 input 47 48 49 50 51 52 53 54 the address bus (a8-a0) selects specific registers during d3mx register accesses. a8/trs 55 the test register select (trs) signal discriminates between normal and test mode register accesses. trs is high during test mode register accesses, and is low during normal mode register accesses. the trs input has an integral pull down resistor. trs should be connected to ground for normal mode register access. rstb input 58 the active low reset (rstb) signal provides an asynchronous d3mx reset. rstb is a schmitt triggered input with an integral pull up resistor.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 32 pin name type pin no. function ale input 46 the address latch enable (ale) is active high and latches the address bus (a7-a0) and trs when low. when ale is high, the internal address latches are transparent. it allows the d3mx to interface to a multiplexed address/data bus. the ale input has an integral pull up resistor. vddi1 vddi2 power 60 189 the core power (vddi) pins should be connected to a well decoupled +5 v dc in common with vddo. vssi1 vssi2 ground 59 191 the core ground (vssi) pins should be connected to gnd in common with vsso. vddo1 vddo2 vddo3 vddo4 vddo5 vddo6 power 199 9 43 95 121 164 the pad ring power (vddo) pins should be connected to a well decoupled +5 v dc in common with vddi. vsso1 vsso2 vsso3 vsso4 vsso5 vsso6 vsso7 vsso8 vsso9 vsso10 ground 200 8 36 96 111 163 183 27 80 132 the pad ring ground (vsso) pins should be connected to gnd in common with vssi.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 33 notes on pin description: all d3mx inputs and bidirectionals present minimum capacitive loading and operate at ttl logic levels. all d3mx digital outputs and bidirectionals have 2 ma drive capability, except the intb, tpos/tdat, tneg/tmfp, tclk, roclk, rodat, rmfp, rmsfp, rohp outputs and the d7-d0 bidirectionals, which have 4 ma drive capability. the vsso and vssi ground pins are not internally connected together. failure to connect these pins externally may cause malfunction or damage the d3mx. the vddo and vddi power pins are not internally connected together. failure to connect these pins externally may cause malfunction or damage the d3mx. 208-pin qfp pins # 13, 28, 40, 61, 67, 73, 79, 85, 93, 113, 119, 125, 131, 140, 147, 165, 171, 178, 185, 192, 197 are all "no-connect".
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 34 8 functional description 8.1 ds3 framer the ds3 framer (frmr) block integrates circuitry required for decoding a b3zs-encoded signal and framing to the resulting ds3 bit stream. the frmr is directly compatible with the m23 and c-bit parity ds3 applications. the frmr decodes a b3zs-encoded signal and provides indications of line code violations. the b3zs decoding algorithm and the lcv definition can independently be chosen via software. loss of signal is also detected. the framing algorithm examines five f-bit candidates simultaneously. when at least one discrepancy has occurred in all the candidates, the algorithm examines the next set of candidates. when a single f-bit candidate remains in a set, the first bit in the supposed m-subframe is examined for the m-frame alignment signal (i.e. the m-bits, m1,m2,m3, are following the 010 pattern). framing is declared if the m-bits are correct for three consecutive m-frames while no discrepancies have occurred in the f-bits. during the examination of the m-bits the x-bits and p-bits are ignored. the algorithm gives a maximum average reframe time of less than 1.5 ms. once in-frame, the frmr provides indications of the m-frame and m-subframe boundaries, and identifies the overhead bit positions in the incoming ds3 signal. while the frmr is in-frame, the f-bit and m-bit positions in the ds3 stream are examined. out-of-frame is declared when 3 f-bit errors out of 16 consecutive f- bits or 8 consecutive f-bits are observed (selectable by the m3o8 bit), or when one or more m-bit errors are detected in 3 out of 4 consecutive m-frames. the m-bit error criteria for oof can be disabled via the mbdis bit in the ds3 framer configuration register. the 3 out of 8 consecutive f-bits out-of-frame ratio provides more robust operation in the presence of a 10 - 3 bit error rate than the 3 out of 16 consecutive f-bits ratio (less than one false oof every minute verses one false oof every 6 seconds, respectively); either choice of out-of-frame ratios allows an out-of-frame to be declared quickly when the m-subframe alignment patterns or, optionally, when the m-frame alignment is lost. also while in-frame, m-bit or f-bit framing bit errors and p-bit parity errors are indicated. when c-bit parity mode is enabled, both c-bit parity errors and far end block errors are indicated. these error indications, as well as the line code violation and excessive zeros indication, may be accumulated over 1 second intervals with the t3 performance monitor (pmon). note that the framer is an
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 35 off-line framer, indicating both oof and cofa events. even if an oof is indicated, the framer will continue indicating performance monitoring information based on the previous frame alignment. status signals such as the red alarm, alarm indication signal, and the idle signal are detected. the framer employs a simple integration algorithm (with a 1:1 slope) that is based on the occurrence of "valid" m-frame intervals. for the red alarm, an m-frame is said to be a "valid" interval if it contains a red defect, defined as an occurrence of an oof or los event during that m-frame. for ais and idle, an m-frame is said to be a "valid" interval if it contains ais or idle, defined as the occurrence of less than 15 discrepancies in the expected signal pattern ("1010" or "1111" for ais; "1100" for idle) while valid frame alignment is maintained. the discrepancy threshold ensures the detection algorithms operate in the presence of bit error rates of up to 10 -3 . for ais, the expected pattern may be selected to be: the framed "1010" signal; the framed arbitrary ds3 signal and the c-bits all zero; the framed "1010" signal and the c-bits all zero; the framed all-ones signal (with overhead bits ignored); or the unframed all-ones signal (with overhead bits equal to ones). each "valid" m-frame interval causes an associated integration counter to increment; "non-valid" m-frames cause a decrement. with the slow detection option, red, ais, or idle is declared if the associated count saturates at 127 which results in a detection time of 13.5 ms. with the fast detection option, red, ais, or idle is declared if the associated count saturates at 21 which results in a detection time of 2.23 ms. red, ais, or idle declaration is deasserted when the associated interval count decrements to 0. valid x-bits are extracted by the frmr to provide indication of far end receive failure. the ferf status is set to logic 1 if the extracted x-bits are equal and are logic 0 (i.e. x1=x2=0); the status is set to logic 0 if the extracted x-bits are equal and are logic 1(i.e. x1=x2=1). if the x-bits are not equal, the ferf status remains in its previous state. the extracted ferf status is buffered for 2 m- frames before being reported within the ds3 frmr status register or being output on the rferf pin. this buffer ensures a better than 99.99% chance of freezing the ferf status on a correct value during the occurrence of an out of frame. when an oof occurs, the ferf value is held at the state contained in the buffer location corresponding to the second to last m-frame. this location is not updated until the oof condition is deasserted. meanwhile, the buffer location corresponding to the last m-frame is continually updated every m-frame based on the above ferf definition. once correct frame alignment has been found and oof is deasserted, the buffer location corresponding to the last m- frame will contain valid ferf status and the buffer location corresponding to the second to last m-frame is enabled to be updated every m-frame.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 36 when enabled for c-bit parity operation, both the far end alarm and control channel and the path maintenance data link are extracted and serialized at 9.4 kbit/s and 28.2 kbit/s, respectively. codes in the extracted far end alarm and control (feac) channel may be detected with the bit-oriented code detector (rboc). hdlc messages in the extracted path maintenance data link may be received with the data link receiver (rfdl). the frmr may be configured for c-bit parity mode or left in m23 mode. when c-bit parity mode is not enabled, outputs relating to c-bit parity features are forced to an inactive state. the frmr, however, provides an indication of whether the c-bit parity application is present or absent, independent of how it is configured. the frmr may be configured to generate interrupts on error events or status changes. all sources of interrupts can be masked or acknowledged via internal registers. internal registers are also used to configure the frmr. access to these registers is via a generic microprocessor bus. under ds3 ais, lof or los conditions, the m23 and m12 multiplexers can receive data which corresponds to a continuous c-bit stuff ratio of between 0 and 100%. at the extremes of the stuff ratio (i.e. 0% and 100%) the recovered ds1/e1 tributary clocks will exceed their nominal value by up to +/-1750 ppm. this tributary frequency excursion could pose a problem for downstream circuitry in some applications. 8.2 ds3 performance monitor the ds3 performance monitor (pmon) block interfaces directly with the t3 framer (frmr) to accumulate line code violation (lcv) events, excessive zeros occurrences (exzs), p-bit parity error (perr) events, c-bit parity error (cperr) events, far end block error (febe) events, and framing bit error (ferr) events in counters over intervals which are defined by successive microprocessor writes to a pmon counter register location. each counter saturates at a specific value. due to the off-line nature of the t3 framer, pmon continues to accumulate error events even while the frmr is indicating oof. when a microprocessor write to a pmon count register is performed, a transfer clock signal is generated. this transfer clock causes the pmon block to transfer the current counter values into holding registers and reset the counters to begin accumulating error events for the next interval. the counters are reset in such a manner that error events occurring during the reset period are not missed.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 37 whenever counter data is transferred into the holding registers, an interrupt is generated, providing the interrupt is enabled. if the holding registers have not been read since the last interrupt, an overrun status bit is set. 8.3 path maintenance data link receiver the rfdl data link receiver is a microprocessor peripheral used to receive lapd/hdlc frames from the ds3 c-bit parity path maintenance data link the rfdl detects the change from flag characters to the first byte of data, removes stuffed zeros on the incoming data stream, receives frame data, and calculates the crc-ccitt frame check sequence (fcs). received data is placed into a 4-level fifo buffer. the status register contains bits which indicate overrun, end of message, flag detected, and buffered data available. on end of message, the status register also indicates the fcs status and the number of valid bits in the final data byte. interrupts are generated when one, two or three (programmable count) bytes are stored in the fifo buffer. interrupts are also generated when the terminating flag sequence, abort sequence, or fifo buffer overrun are detected. 8.4 alarm and control channel bit oriented code detector the bit-oriented code detector (rboc) block detects the presence of 63 of the 64 possible bit-oriented codes (bocs) transmitted in the ds3 c-bit parity far-end alarm and control (feac) channel. the 64 th code ("111111") is similar to the hdlc flag sequence and is ignored. bit-oriented codes are received on the feac channel as 16-bit sequences each consisting of 8 ones, a zero, 6 code bits, and a trailing zero ("111111110xxxxxx0"). bocs are validated when repeated at least 10 times . the rboc can be enabled to declare a received code valid if it has been observed for 8 out of 10 times or for 4 out of 5 times, as specified by the avc bit in the rboc configuration/interrupt enable register. valid bocs are indicated through the rboc interrupt status register. the boc bits are set to all ones ("111111") if no valid code has been detected. the rboc can be programmed to generate an interrupt when a detected code has been validated and when the code disappears.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 38 8.5 ds3 transmitter the tran t3 transmitter integrates circuitry required to insert the overhead bits into a ds3 bit stream and produce a b3zs encoded signal. the tran is directly compatible with the m23 and c-bit parity ds3 formats specified in ansi t1.107a. when configured for the c-bit parity application, all overhead bits are inserted. when configured for the m23 application, all overhead bits except the stuff control bits (the c-bits) are inserted; the c-bits must be inserted by upstream circuitry (such as the mx23 tsb). the tran provides indication of the m-frame boundary in the outgoing ds3 signal. the ds3 signal may optionally be encoded in b3zs format. status signals such as far end receive failure, the alarm indication signal, and the idle signal can be inserted when their transmission is enabled by internal register bits. a valid pair of p-bits is automatically calculated and inserted by the tran. when c-bit parity mode is selected, the c-bit parity bits, and far end block error (febe) indications are automatically inserted. when enabled for c-bit parity operation, the alarm and control channel and the path maintenance data link are input serially at 9.4 kbit/s and 28.2 kbit/s, respectively, and inserted into the appropriate overhead bits. codes to be inserted into the alarm and control channel are sourced by the xboc bit- oriented code transmitter tsb. lapd messages to be inserted in the path maintenance data link are sourced by the xfdl data link transmitter. the tran supports diagnostic modes in which it inserts p or c-bit parity errors, f-bit framing errors, m-bit framing errors, invalid x or p-bits, line code violations, or all-zeros. 8.6 path maintenance data link transmitter the xfdl data link transmitter is designed to provide a serial path maintenance hdlc data link for the ds3 c-bit parity application. the xfdl is used under microprocessor to transmit hdlc data frames. it performs all of the data serialization, crc generation, zero-bit stuffing, as well as flag, idle, and abort sequence insertion. data to be transmitted is provided on an interrupt- driven basis by writing to a double-buffered transmit data register. upon completion of the frames, a crc-ccitt frame check sequence is transmitted, followed by idle flag sequences. if the transmit data register underflows, an abort sequence is automatically transmitted.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 39 when enabled, the xfdl continuously transmits the flag character (01111110). data bytes to be transmitted are written into the transmit data register. after the parallel-to-serial conversion of each data byte, an interrupt is generated to signal the controller to write the next byte into the transmit data register. after the last data frame byte, the crc word (if crc insertion has been enabled), or a flag (if crc insertion has not been enabled) is transmitted. the xfdl then returns to the transmission of flag characters. the last data frame byte can be indicated by either writing to the eom bit in the xfdl configuration register or by setting the tdleomi input high. if there are more than five consecutive ones in the raw transmit data or in the crc data, a zero is stuffed into the serial data output. this prevents the unintentional transmission of flag or abort characters. abort characters can be continuously transmitted at any time by setting a control bit. during transmission, an underrun situation can occur if data is not written to the transmit data register before the previous byte has been depleted. in this case, an abort sequence is transmitted, and the controlling processor is notified via the udr status bit. 8.7 alarm and control channel bit oriented code transmitter the xboc bit-oriented code transmitter tsb transmits 63 of the possible 64 bit-oriented codes (bocs) over the ds3 c-bit parity far end alarm and control (feac) channel. the 64 th possible code (111111) is similar to the hdlc idle sequence and is used in the xboc to disable transmission of any bit-oriented codes. bocs are transmitted on the feac as a 16 bit sequence consisting of 8 ones, 1 zero, 6 code bits, and 1 trailing zero (111111110xxxxxx0). an internal register is loaded with the 6 code bits to be transmitted. the 16 bit sequence is continuously transmitted until disabled by forcing the six code bits to 111111. 8.8 m23 multiplexer the mx23 m23 multiplexer integrates circuitry required to asynchronously multiplex and demultiplex seven ds2 streams into, and out of, an m23 or c-bit parity formatted ds3 serial stream. when multiplexing seven ds2 streams into an m23 formatted ds3 stream, the mx23 tsb performs rate adaptation to the ds3 by integral fifo buffers, controlled by timing circuitry. the fifo buffers accommodate in excess of 5.0 uipp of sinusoidal jitter on td2clk for all jitter frequencies. the c-bits are also
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 40 generated and inserted by the timing circuitry. software control is provided to transmit ds2 ais and ds2 payload loopback requests. the loopback request is coded by inverting one of the three c-bits (the default option is compatible with ansi t1.107a section 8.2.1 and tr-tsy-000009 section 3.7). the tsb also supports generation of a c-bit parity formatted ds3 stream by providing a generated ds2 rate clock (gd2clk) corresponding to a 100% stuffing ratio. integrated m13 applications are supported by providing a generated ds2 rate clock corresponding to a 39.1% stuffing ratio. when demultiplexing seven ds2 streams from an m23 formatted ds3, the mx23 performs bit destuffing via interpretation of the c-bits. the mx23 also detects and indicates ds2 payload loopback requests encoded in the c-bits. as per ansi t1.107a section 8.2.1 and tr-tsy-000009 section 3.7, the loopback command is identified as c3 being the inverse of c1 and c2. because tr-tsy- 000233 section 5.3.14.1 recommends compatibility with non-compliant existing equipment, the two other loopback command possibilities are also supported. as per tr-tsy-000009 section 3.7, the loopback request must be present for five successive m-frames before declaration of detection. removal of the loopback request is declared when it has been absent for five successive m-frames. ds2 payload loopback can be activated or deactivated under software control. during payload loopback the ds2 stream being looped back still continues unaffected in the demultiplex direction to the ds2 framer. all seven demultiplexed ds2 streams can also be replaced with ais on an individual basis. 8.9 ds2 framer the frmr ds2 framer integrates circuitry required for framing to a ds2 bit stream and is directly compatible with the m12 ds2 application. the frmr can also be configured to frame to a g.747 bit stream. the ds2 frmr frames to a ds2 signal with a maximum average reframe time of less than 7 ms and frames to a g.747 signal with a maximum average reframe time of 1 ms. in ds2 mode, both the f-bits and m-bits must be correct for a significant period of time before frame alignment is declared. in g.747 mode, frame alignment is declared if the candidate frame alignment signal has been correct for 3 consecutive frames (in accordance with ccitt rec. g.747 section 4). once in frame, the ds2 frmr provides indications of the m-frame and m- subframe boundaries, and identifies the overhead bit positions in the incoming ds2 signal or provides indications of the frame boundaries and overhead bit positions in the incoming g.747 signal. depending on configuration, declaration of ds2 out-of-frame occurs when 2 out of 4 or 2 out of 5 consecutive f-bits are in error (these two ratios are
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 41 recommended in tr-tsy-000009 section 4.1.2) or when one or more m-bit errors are detected in 3 out of 4 consecutive m-frames. the m-bit error criteria for oof can be disabled via the mbdis bit in the ds2 framer configuration register. in g.747 mode, out-of-frame is declared when four consecutive frame alignment signals are incorrectly received (in accordance with ccitt rec. g.747 section 4). note that the ds2 framer is an off-line framer, indicating both off and cofa. error events continue to be indicated even when the frmr is indicating oof, based on the previous frame alignment. the red alarm and alarm indication signal are detected by the ds2 frmr in 9.9 ms for ds2 format and in 6.9 ms for g.747 format. the framer employs a simple integration algorithm (with a 1:1 slope) that is based on the occurrence of "valid" ds2 m-frame or g.747 frame intervals. for the red alarm, a ds2 m- frame (or g.747 frame, depending upon the framing format selected) is said to be a "valid" interval if it contains a red defect, defined as the occurrence of an oof event during that m-frame (or g.747 frame). for ais, a ds2 m-frame (or g.747 frame) is said to be a "valid" interval if it contains ais, defined as the occurrence of less than 9 zeros while the framer is out of frame during that m- frame (or g.747 frame). the discrepancy threshold ensures the detection algorithm operates in the presence of bit error rates of up to 10 -3 . each "valid" ds2 m-frame (or g.747 frame) causes an integration counter to increment; "non- valid" ds2 m-frame (or g.747 frame) intervals cause a decrement. red or ais is declared if the associated integrator count saturates at 53, resulting in a detection time of 9.9 ms for ds2 and 6.9 ms for g.747. red or ais declaration is deasserted when the associated count decrements to 0. the ds2 x-bit or g.747 remote alarm indication (rai) bit is extracted by the ds2 frmr to provide an indication of far end receive failure. the ferf status is set to the current x/rai state only if the two successive x/rai bits were in the same state. the extracted ferf status is buffered for 6 ds2 m-frames or 6 g.747 frames before being reported within the ds2 frmr status register. this buffer ensures a virtually 100% probability of freezing the ferf status in a valid state during an out of frame occurrence in ds2 mode, and ensures a better than 99.9% probability of freezing the valid status during an oof occurrence in g.747 mode. when an oof occurs, the ferf value is held at the state contained in the last buffer location corresponding to the previous sixth m-frame or g.747 frame. this location is not updated until the oof condition is deasserted. meanwhile, the last four of the remaining five buffer locations are loaded with the frozen ferf state while the first buffer location corresponding to the current m-frame/ g.747 frame is continually updated every m-frame/g.747 frame based on the above ferf definition. once correct frame alignment has been found and oof is deasserted, the first buffer location will contain a valid ferf status and the
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 42 remaining five buffer locations are enabled to be updated every m-frame or g.747 frame. ds2 m-bit and f-bit framing errors are indicated as are g.747 framing word errors (or bit errors) and g.747 parity errors. these error indications are accumulated for performance monitoring purposes in internal, microprocessor readable counters. the performance monitoring accumulators continue to count error indication even while the framer is indicating oof. the ds2 frmr may be configured to generate interrupts on error events or status changes. all sources of interrupts can be masked or acknowledged via internal registers. internal registers are also used to configure the ds2 frmr. 8.10 m12 multiplexer the mx12 m12 multiplexer integrates circuitry required to asynchronously multiplex and demultiplex four ds1 streams into, and out of, an m12 formatted ds2 serial stream (as defined in ansi t1.107 section 7) and to support asynchronous multiplexing and demultiplexing of three 2048 kbit/s into and out of a g.747 formatted 6312 kbit/s high speed signal (as defined in ccitt rec. g.747). when multiplexing four ds1 streams into an m12 formatted ds2 stream, the mx12 tsb performs logical inversion on the second and fourth tributary streams. rate adaptation to the ds2 is performed by integral fifo buffers, controlled by timing circuitry. the fifo buffers accommodate in excess of 5.0 uipp of sinusoidal jitter on the ds1 clocks for all jitter frequencies. x, f, m, and c bits are also generated and inserted by the timing circuitry. software control is provided to transmit far end receive failure (ferf) indications, ds2 ais, and ds1 payload loopback requests. the loopback request is coded by inverting one of the three c-bits (the default option is compatible with ansi t1.107a section 8.2.1 and tr-tsy-000009 section 3.7).two diagnostic options are provided to invert the transmitted f or m bits. when demultiplexing four ds1 streams from an m12 formatted ds2, the mx12 performs bit destuffing via interpretation of the c-bits. the mx12 also detects and indicates ds1 payload loopback requests encoded in the c-bits. as per ansi t1.107 section 7.2.1.1 and tr-tsy-000009 section 3.7, the loopback command is identified as c3 being the inverse of c1 and c2. because tr-tsy- 000233 section 5.3.14.1 recommends compatibility with non-compliant existing equipment, the two other loopback command possibilities are also supported. as per tr-tsy-000009 section 3.7, the loopback request must be present for five successive m-frames before declaration of detection. removal of the loopback request is declared when it has been absent for five successive m-frames.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 43 ds1 payload loopback can be activated or deactivated under software control. during payload loopback the ds1 stream being looped back still continues unaffected in the demultiplex direction. the second and fourth demultiplexed ds1 streams are logically inverted, and all four demultiplexed ds1 streams can be replaced with ais on an individual basis. similar functionality supports ccitt recommendation g.747. the fifo is still required for rate adaptation. the frame alignment signal and parity bit are generated and inserted by the timing circuitry. software control is provided to transmit remote alarm indication (rai), high speed signal ais, and the reserved bit. a diagnostic option is provided to invert the transmitted frame alignment signal and parity bit. when demultiplexing three 2048 kbit/s streams from a g.747 formatted 6312 kbit/s stream, the mx12 performs bit destuffing via interpretation of the c-bits. tributary payload loopback can be activated or deactivated under software control. although no remote loopback request has been defined for g.747, inversion of the third c-bit triggers a loopback request detection indication in anticipation of recommendation g.747 refinement. all three demultiplexed 2048 kbit/s streams can be replaced with ais on an individual basis. 8.11 loopback modes ds3 diagnostic loopback allows the transmitted ds3 stream to be looped back into the receive ds3 path, overriding the ds3 stream received on the rdat/rpos and rneg/rlcv inputs. the rclk signal is also substituted with the transmit ds3 clock, tclk. while this mode is active, ais may be substituted for the ds3 payload being transmitted on the tpos/tdat and tneg/tmfp outputs. the configuration of the receive interface determines how the tneg/tmfp signal is handled during loopback: if the uni bit in the ds-3 frmr is set, then the receive interface is configured for rdat and rlcv, therefore the tneg/tmfp signal is suppressed during loopback so that transmit mfp indications will not be seen nor accumulated as input lcvs; if the uni bit is clear, then the interface is configured for bipolar signals rpos and rneg, therefore the tneg is fed directly to the rneg input. this loopback mode is shown diagrammatically, below:
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 44 figure 2 - ds3 diagnostic loopback mx12 #7 f r m r mx12 #6 f r m r mx12 #5 f r m r mx12 #4 f r m r mx12 #3 f r m r mx12 #2 f r m r ds3 frmr ds3 tran mx23 mx12 #1 f r m r rclk rpos/ rdat rneg/ rlcv tclk tpos/ tdat tneg/ tmfp uni optional ais insertion ds3 line loopback allows the received ds3 stream to be looped back into the transmit ds3 path, overriding the ds3 stream created internally by the multiplexing of the lower speed tributaries. the transmit signals on tpos/tdat and tneg/tmfp are substituted with the receive signals on rpos/rdat and rneg/rlcv. the tclk signal is also substituted with the receive ds3 clock, rclk. while this mode is active, ais may be substituted for the ds3 payload being transmitted on the tpos/tdat and tneg/tmfp outputs. note that the transmit interface must be configured to be the same as the ds3-frmr receive interface for this mode to work properly. this loopback mode is shown diagrammatically, below:
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 45 figure 3 - ds3 line loopback mx12 #7 f r m r mx12 #6 f r m r mx12 #5 f r m r mx12 #4 f r m r mx12 #3 f r m r mx12 #2 f r m r ds3 frmr ds3 tran mx23 mx12 #1 f r m r rclk rpos/ rdat rneg/ rlcv tclk tpos/ tdat tneg/ tmfp ds2/g.747 demultiplex loopback allows each of the seven demultiplexed ds2 or g.747 streams to be looped back into the mx23 and multiplexed up into the transmit ds3 stream, overriding the tributary ds2 stream coming from the mx12. this loopback mode is shown diagrammatically, below: figure 4 - ds2/g.747 demultiplex loopback mx12 #7 f r m r mx12 #6 f r m r mx12 #5 f r m r mx12 #4 f r m r mx12 #3 f r m r mx12 #2 f r m r ds3 frmr ds3 tran mx23 mx12 #1 f r m r rclk rpos/ rdat rneg/ rlcv tclk tpos/ tdat tneg/ tmfp optional demux ais insertion ds2/g.747 tributary loopback path
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 46 ds1/e1 demultiplex loopback allows each of the four demultiplexed ds1 or e1 streams to be looped back into the mx12 and ultimately multiplexed into the transmit ds3 stream, overriding the tributary ds1 or e1 stream coming from the t1dat and t1clk inputs. this loopback mode is shown diagrammatically, below: figure 5 - ds1/e1 demultiplex loopback mx12 #7 f r m r mx12 #6 f r m r mx12 #5 f r m r mx12 #4 f r m r mx12 #3 f r m r mx12 #2 f r m r ds3 frmr ds3 tran mx23 mx12 #1 f r m r rclk rpos/ rdat rneg/ rlcv tclk tpos/ tdat tneg/ tmfp rd1datn rd1clkn td1datn td1clkn ds1/e1 tributary loopback path optional demux ais insertion 8.12 microprocessor interface the microprocessor interface block provides normal and test mode registers, the interrupt logic, and the logic required to connect to the microprocessor interface. the normal mode registers are required for normal operation, and test mode registers are used to enhance the testability of the d3mx. the register set is accessed as follows:
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 47 9 register memory map address register 00h master reset/clock status 01h revision/global pmon update 02h master bypass configuration 03h master hdlc configuration 04h master loopback configuration 05h master interface configuration 06h master alarm enable/network requirement bit 07h master test 08h master interrupt source #1 09h master interrupt source #2 0ah master interrupt source #3 0bh reserved 0ch ds3 tran configuration 0dh ds3 tran diagnostic 0eh ds3 tran reserved 0fh ds3 tran reserved 10h reserved for ds3 pmon test 11h ds3 pmon interrupt enable/status 12h - 13h reserved 14h ds3 pmon lcv count (lsb) 15h ds3 pmon lcv count (msb) 16h ds3 pmon ferr count (lsb) 17h ds3 pmon ferr count (msb) 18h ds3 pmon exzs count (lsb) 19h ds3 pmon exzs count (msb) 1ah ds3 pmon perr count (lsb)
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 48 address register 1bh ds3 pmon perr count (msb) 1ch ds3 pmon cperr count (lsb) 1dh ds3 pmon cperr count (msb) 1eh ds3 pmon febe count (lsb) 1fh ds3 pmon febe count (msb) 20h xfdl tsb configuration 21h xfdl tsb interrupt status 22h xfdl tsb transmit data 23h xfdl reserved 24h rfdl tsb configuration 25h rfdl tsb interrupt control/status 26h rfdl tsb status 27h rfdl tsb receive data 28h mx23 configuration 29h mx23 demux ais insert 2ah mx23 mux ais insert 2bh mx23 loopback activate 2ch mx23 loopback request insert 2dh mx23 loopback request detect 2eh mx23 loopback request interrupt 2fh mx23 reserved 30h feac xboc reserved 31h feac xboc code 32h feac rboc configuration/interrupt enable 33h feac rboc interrupt status 34h ds3 frmr configuration 35h ds3 frmr interrupt enable/additional configuration
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 49 address register 36h ds3 frmr interrupt status 37h ds3 frmr status 38h - 3fh reserved 40h ds2 #1 frmr configuration 41h ds2 #1 frmr interrupt enable 42h ds2 #1 frmr interrupt status 43h ds2 #1 frmr status 44h ds2 #1 frmr monitor interrupt enable/status 45h ds2 #1 frmr ferr count 46h ds2 #1 frmr perr count (lsb) 47h ds2 #1 frmr perr count (msb) 48h ds2 #1 mx12 configuration and control 49h ds2 #1 mx12 loopback code select 4ah ds2 #1 mx12 ais insert 4bh ds2 #1 mx12 loopback activate 4ch ds2 #1 mx12 loopback interrupt 50h - 57h ds2 #2 frmr registers 58h - 5ch ds2 #2 mx12 registers 60h - 67h ds2 #3 frmr registers 68h - 6ch ds2 #3 mx12 registers 70h - 77h ds2 #4 frmr registers 78h - 7ch ds2 #4 mx12 registers 80h - 87h ds2 #5 frmr registers 88h - 8ch ds2 #5 mx12 registers 90h - 97h ds2 #6 frmr registers 98h - 9ch ds2 #6 mx12 registers a0h - a7h ds2 #7 frmr registers a8h - ach ds2 #7 mx12 registers
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 50 address register ach - ffh reserved 100h-1ffh reserved for test for all register accesses, csb must be low.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 51 10 normal mode register description normal mode registers are used to configure and monitor the operation of the d3mx. normal mode registers (as opposed to test mode registers) are selected when trs (a[8]) is low. notes on normal mode register bits: 1. writing values into unused register bits typically has no effect. however, to ensure software compatibility with future, feature-enhanced versions of the product, unused register bit must be written with logic 0. reading back unused bits can produce either a logic 1 or a logic 0; hence unused register bits should be masked off by software when read. 2. all configuration bits that can be written into can also be read back. this allows the processor controlling the d3mx to determine the programming state of the block. 3. writeable normal mode register bits are cleared to logic 0 upon reset unless otherwise noted. 4. writing into read-only normal mode register bit locations does not affect d3mx operation unless otherwise noted.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 52 register 00h: master reset / clock status bit type function default bit7 r ds3rcact x bit6 r ds3tcact x bit5 r ds2tcact x bit4 unused x bit3 unused x bit2 unused x bit1 unused x bit0 r/w reset 0 the master reset register is provided at d3mx read/write address 00h. reset: the reset bit implements a software reset. if the reset bit is a logic 1, the entire d3mx is held in reset. this bit is not self-clearing; therefore, a logic 0 must be written to bring the d3mx out of reset. holding the d3mx in a reset state effectively puts it into a low power, stand-by mode. a hardware reset clears the reset bit, thus deasserting the software reset. ds3rcact: the ds3 receive clock activity (ds3rcact) bit indicates at least one low to high transition has occurred on the rclk input since the last read of this register. the ds3rcact bit is set to a logic 1 by a rising edge on the rclk input and is cleared to a logic 0 by a read of this register. ds3tcact: the ds3 transmit clock activity (ds3tcact) bit indicates at least one low to high transition has occurred on the ticlk input since the last read of this register. the ds3tcact bit is set to a logic 1 by a rising edge on the ticlk input and is cleared to a logic 0 by a read of this register. ds2tcact: the ds2 transmit clock activity (ds2tcact) bit indicates at least one low to high transition has occurred on the td2clk input since the last read of this register. the ds2tcact bit is set to a logic 1 by a rising edge on the
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 53 td2clk input and is cleared to a logic 0 by a read of this register. note that if the td2clk signal is absent for a period of time (i.e., td2clk clock failure), the d3mx must be reset once the td2clk signal is restored.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 54 register 01h: revision/global pmon update bit type function default bit7 r id7 0 bit6 r id6 0 bit5 r id5 0 bit4 r id4 0 bit3 r id3 0 bit2 r id2 0 bit1 r id1 0 bit0 r id0 0 the revision/global pmon update register is provided at d3mx read/write address 01h. id[7:0] the version identification bits id[7:0], are set to a fixed value representing the version number of the d3mx. these bits can be read by software to determine the version number. writing to this register causes all performance monitor counters (ds3 and ds2/g.747) to be updated simultaneously.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 55 register 02h: master bypass configuration bit type function default bit7 r/w exd2clk 0 bit6 r/w byp7 0 bit5 r/w byp6 0 bit4 r/w byp5 0 bit3 r/w byp4 0 bit2 r/w byp3 0 bit1 r/w byp2 0 bit0 r/w byp1 0 the master bypass configuration register is provided at d3mx read/write address 02h. byp[7:1]: the byp[7:1] bits allow for each of the seven mx12 blocks to be individually bypassed so that an external ds2 may be multiplexed and demultiplexed directly without the intermediate m12 multiplexing. if byp[n] is a logic 1, the following applies: 1. a nominally 6.312 mhz clock is expected on td1clk(4n). 2. a data stream synchronous to td1clk(4n) is expected on td1dat(4n). 3. the clocks on td1clk(4n-1), td1clk(4n-2) and td1clk(4n-3) have no effect. 4. the data streams on td1dat(4n-1), td1dat(4n-2) and td1dat(4n-3) are ignored. 5. a nominally 6.312 mhz clock is presented on rd1clk(4n). 6. a data stream synchronous to rd1clk(4n) is presented on rd1dat(4n). 7. the signals on rd1clk(4n-1), rd1clk(4n-2), rd1clk(4n-3), rd1dat(4n-1), rd1dat(4n-2) and rd1dat(4n-3) are always low.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 56 exd2clk bit: the exd2clk bit selects between an internally generated ds2 clock and the clock input on the td2clk pin. if exd2clk is a logic 0, the ds2 clock for the multiplexing side becomes the generated clock derived from the ds3 transmit ticlk clock. the generated ds2 clock is nominally 6.306272 mhz while in c-bit parity mode and while in m23 mode, it is nominally 6.311993 mhz. if exd2clk is a logic 1, the transmit ds2 clock becomes td2clk.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 57 register 03h: master hdlc configuration bit type function default bit7 r/w rexhdlc 0 bit6 r/w texhdlc 1 bit5 unused x bit4 unused x bit3 r/w reompol 0 bit2 r/w tudrpol 0 bit1 r/w rintpol 0 bit0 r/w tintpol 0 the master hdlc configuration register is provided at d3mx read/write address 03h. rexhdlc: the state of the receive external hdlc (rexhdlc) bit determines whether the c-bit parity path maintenance data link is terminated by the internal hdlc receiver or by an external hdlc receiver. when the rexhdlc bit is a logic 0, the internal hdlc receiver is selected; the rdlclk/rdlint pin is configured to output the interrupt signal (rdlint) from the internal hdlc receiver and the rdlsig/rdleom pin is configured to output the end-of- message signal (rdleom) from the internal hdlc receiver. when the rexhdlc bit is a logic 1, the use of an external hdlc receiver is selected; the rdlsig/rdleom pin is configured to output the data link data stream (rdlsig) and the rdlclk/rdlint pin is configured to output the data link clock signal (rdlclk). the rexhdlc bit is cleared to logic 0 upon reset. texhdlc: the state of the transmit external hdlc (texhdlc) bit determines whether the c-bit parity path maintenance data link is sourced by the internal hdlc transmitter or by an external hdlc transmitter. when the texhdlc bit is a logic 0, the internal hdlc transmitter is selected; the tdlclk/tdlint pin is configured as an output to present the interrupt signal (tdlint) from the internal hdlc transmitter and the tdlsig/tdludr pin is configured to output the underrun signal (tdludr) from the internal hdlc transmitter. when the texhdlc bit is a logic 1, the use of an external hdlc transmitter is selected; the tdlsig/tdludr pin is configured to input the data link data
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 58 stream (tdlsig) and the tdlclk/tdlint pin is configured to output the data link clock signal (tdlclk). the texhdlc bit is set to logic 1 upon reset. reompol: the receive end-of-message polarity (reompol) bit determines the assertion level of the rdleom output. if reompol is a logic 0, the rdleom output is an active low open-drain output. if reompol is a logic 1, the rdleom output is asserted high and always has a strong drive. if the rexhdlc bit is a logic 1, this bit has no effect. tudrpol: the transmit underflow polarity (tudrpol) bit determines the assertion level of the tdludr output. if tudrpol is a logic 0, the tdludr output is an active low open-drain output. if tudrpol is a logic 1, the tdludr output is asserted high and always has a strong drive. if the texhdlc bit is a logic 1, this bit has no effect. rintpol: the receive interrupt polarity (rintpol) bit determines the assertion level of the rdlint output. if rintpol is a logic 0, the rdlint output is an active low open-drain output. if rintpol is a logic 1, the rdlint output is asserted high and always has a strong drive. if the rexhdlc bit is a logic 1, this bit has no effect. tintpol: the transmit interrupt polarity (tintpol) bit determines the assertion level of the tdlint output. if tintpol is a logic 0, the tdlint output is an active low open-drain output. if tintpol is a logic 1, the tdlint output is asserted high and always has a strong drive. if the texhdlc bit is a logic 1, this bit has no effect.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 59 register 04h: master loopback configuration bit type function default bit7 unused x bit6 unused x bit5 unused x bit4 unused x bit3 r/w lineais[1] 0 bit2 r/w lineais[0] 0 bit1 r/w llbe 0 bit0 r/w dlbe 0 the master loopback configuration register is provided at d3mx read/write address 04h. dlbe: the diagnostic loopback enable (dlbe) bit allows the looping back of the transmitted ds3 into the receive ds3 path for diagnostic purposes. if the dlbe bit is a logic 1, the tpos, tneg, and tclk signals are connected internally to replace the signals normally input on the rpos, rneg, and rclk pins. llbe: the line loopback enable (llbe) bit allows the looping back of the received ds3 into the transmit ds3 path. if the llbe bit is a logic 1, the rpos, rneg, and rclk signals are connected internally to replace the signals normally output on the tpos, tneg, and tclk pins. lineais[1:0] the line ais (lineais[1:0]) bits allow the generation of various ais patterns on the tdat output when tuni is set to logic 1, or on the tpos and tneg outputs when tuni is set to logic 0, independent of the data stream being transmitted. the lineais[1:0] option is expected to be used when the diagnostic loopback is invoked, ensuring that only a valid ds3 stream enters the network. the lineais[1:0] bits select one of the following ais patterns for transmission:
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 60 lineais[1:0] ais transmitted 00 none 01 framed, repetitive 1010 pattern with c-bits forced to logic 0 10 framed, repetitive 1111 pattern with c-bits forced to logic 0 11 unframed, all-ones pattern the lineais[1:0]= 01 option is compatible with tr-tsy-000009 section 3.7 objectives. if the intention is to loopback the ais, the ais bit in the ds3 tran configuration register should be written instead.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 61 register 05h: master interface configuration bit type function default bit7 unused x bit6 unused x bit5 unused x bit4 r/w tinv 0 bit3 r/w trise 0 bit2 r/w tuni 0 bit1 r/w rinv 0 bit0 r/w rfall 0 the master interface configuration register is provided at d3mx read/write address 05h. rfall: the receive falling edge select (rfall) bit configures the sampling edge used on the ds3 receive interface. when rfall is a logic 1, the ds3 receive interface is sampled on the falling edge of rclk. when rfall is a logic 0, the ds3 receive interface is sampled on the rising edge of rclk. rinv: the receive invert (rinv) bit enables data inversion of the ds3 receive interface. when rinv is a logic 1, the rpos and rneg signals are active low. when rinv is a logic 0, the rpos and rneg signals are active high. inversion only takes place when the ds3 receive interface is configured for dual rail operation. tuni: the transmit unipolar (tuni) bit configures the ds3 transmit interface for unipolar or dual rail operation. when tuni is a logic 1, the ds3 transmit interface is configured as tdat and tmfp. when tuni is a logic 0, the ds3 transmit interface is configured as tpos and tneg. trise: the transmit falling edge select (trise) bit configures the updating edge used on the ds3 transmit interface. when trise is a logic 1, the ds3
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 62 transmit interface is updated on the rising edge of tclk. when trise is a logic 0, the ds3 transmit interface is updated on the falling edge of tclk. tinv: the transmit invert (tinv) bit enables data inversion of the ds3 transmit interface. when tinv is a logic 1, the tpos and tneg signals are active low. when tinv is a logic 0, the tpos and tneg signals are active high. inversion only takes place when the ds3 transmit interface is configured for dual rail operation.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 63 register 06h: master alarm enable/network requirement bit bit type function default bit 7 r/w tnr 1 bit 6 r rnr x bit 5 r/w altfebe 0 bit 4 r/w redo 0 bit 3 r/w red2alme 0 bit 2 r/w ds2alme 0 bit 1 r/w red3alme 0 bit 0 r/w ds3alme 0 the master alarm enable/network requirement bit register is provided at d3mx read/write address 06h. ds3alme: the ds3 alarm enable (ds3alme) bit allows the automatic generation of ais in all of the demultiplexed ds2s upon a ds3 alarm condition. if ds3alme is a logic 1, a ds3 loss of signal (>175 zeros), a ds3 out-of-frame (oof) condition (i.e. immediately after 3-of-n f-bit errors where n is 8 or 16, or 3-of-4 m-frames containing m-bit errors), ds3 idle code detection or ds3 ais detection causes all of the ds2s to be replaced by an unframed all ones pattern immediately. generation of ais continues while the detected alarm condition persists. if ds3alme is a logic 0, ais can still be generated in the demultiplexed ds2s under software control by setting the bits in the mx23 demux ais insert register. red3alme: the red ds3 alarm enable (red3alme) bit works in conjunction with the ds3alme and enables detection of ds3 red condition to be used in place of ds3 loss of signal and ds3 out-of-frame in the above criteria for demultiplexed ais generation. when ds3alme is set to logic 1 and redalme is set to logic 1, the occurrence of los or oof for 127 consecutive m-frames (or 21 consecutive m-frames, if fdet is set to logic 1 in the ds3 frmr configuration register) causes a ds3 red alarm condition and generates the ds2 ais. when ds3alme is set to logic 1 and redalme is set to logic 0, any occurrence of los or oof generates the ds2 ais. if ds3alme is a logic 0, the redalme bit is ignored.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 64 ds2alme: the ds2 alarm enable (ds2alme) bit allows the automatic generation of ais in the ds1s demultiplexed from a ds2 or g.747 stream which is in an alarm condition. if ds2alme is a logic 1,a ds2 or g.747 out-of-frame (oof) condition (i.e. immediately after 2-of-n f-bit errors where n is 4 or 5, or 3-of-4 m-frames containing m-bit errors for ds2, or immediately after 4 consecutive framing word errors for g.747) or detection of ds2 or g.747 ais causes each of the associated ds1s to be replaced by an unframed all ones pattern immediately. if ds2alme is a logic 0, ais can still be generated in the demultiplexed ds1s under software control by setting the bits in the appropriate mx12 ais insert register. note that the removal of the auto all- ones insertion is performed upon the first ds2 m-frame or g.747 frame pulse after the ds2 frmr has found frame alignment. red2alme: the red ds2 alarm enable (red2alme) bit works in conjunction with the ds2alme and enables detection of ds2 red condition to be used in place of ds2/g.747 out-of-frame in the above criteria for demultiplexed ais generation. when ds2alme is set to logic 1 and red2alme is set to logic 1, the occurrence of oof for 53 consecutive ds2/g.747 "m-frames" causes a ds2 red alarm condition and generates the ds1 ais. when ds2alme is set to logic 1 and red2alme is set to logic 0, any occurrence of oof generates the ds1 ais. if ds2alme is a logic 0, the red2alme bit is ignored. redo: the red alarm output enable (redo) bit selects the type of signal output on the roof/rred pin. if redo is a logic 1, the ds3 red status signal is available on the roof/rred output pin. if redo is a logic 0, the ds3 oof status signal is available on the roof/rred output pin. altfebe: the alternate far end block error (altfebe) bit selects the error conditions detected to define a febe indication. if altfebe is a logic 1, a febe indication is generated in the outgoing c-bit parity ds3 transmit stream if a c- bit parity error occurred in the last received m-frame. if no c-bit parity error occurred, no febe is generated. if altfebe is a logic 0, a febe indication is generated if either one or more framing bit errors or a c-bit parity error has occurred in the last received m-frame. if no framing bit errors nor c-bit parity errors have occurred, then no febe is generated.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 65 rnr: the receive network requirement (rnr) bit reflects the real time value of the network requirement (n r ) bit presented in the second c-bit in m- subframe 1 when in ds3 c-bit parity mode. the rnr bit is a logic 1 if a logic one occurs in the n r overhead bit timeslot. if c-bit parity is not selected, the value of rnr is meaningless and random. tnr: the transmit network requirement (tnr) bit determines the value inserted into the network requirement (n r ) bit transmitted in the second c-bit in m- subframe 1 when in ds3 c-bit parity mode. a logic 1 in the tnr bit causes a one to be transmitted in the n r overhead bit timeslot. the tnr bit is set to a logic 1 upon either a hardware or software reset. if c-bit parity is not selected, the tnr bit has no effect. note that the serial control input, tohen, takes precedence over the effect of this bit when tohen is asserted during the network requirement bit position. while tohen is asserted at the second c-bit position of m-subframe 1, the data on the toh input is transmitted in the n r bit. when the device is set for transmission of ais (register 0ch bit 6) in c-bit parity mode, all c-bits are forced to 0 except for the network requirement bit which is forced to the tnr register bit value. the tnr bit must be cleared when tran is enabled to generate ais in c-bit parity mode.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 66 register 07h: master test bit type function default bit 7 r/w vclk_iotst x bit 6 unused x bit 5 unused x bit 4 w pmctst x bit 3 w dbctrl x bit 2 r/w iotst x bit 1 w hizdata x bit 0 r/w hizio x the master test register is provided at d3mx read/write address 07h. this register is used to select d3mx test features. all bits, except for pmctst, are reset to zero by a hardware reset of the d3mx; a software reset of the d3mx does not affect the state of the bits in this register. vclk_iotst: the vclk_iotst bit replaces the rclk/vclk input as the test clock when the iotst bit is a logic 1. some sense points require a rising edge on the test clock to clock in the value on the pin. this bit satisfies the requirement without needing the rclk/vclk input to toggle. pmctst: the pmctst bit is used to configure the d3mx for pmc's manufacturing tests. when pmctst is set to logic 1, the d3mx microprocessor port becomes the test access port used to run the pmc "canned" manufacturing test vectors. the pmctst bit is logically "ored" with the iotst bit, and can only be cleared by setting csb to logic 1. dbctrl: the dbctrl bit is used to pass control of the data bus drivers to the csb pin while iotst is a logic 1. when the dbctrl bit is set to logic 1, the csb pin controls the output enable for the data bus. while the dbctrl bit is set, holding the csb pin high causes the d3mx to drive the data bus and holding the csb pin low tri-states the data bus. the dbctrl bit overrides the hizdata bit. the dbctrl bit is used to measure the drive capability of the
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 67 data bus driver pads. when iotst and pmctst are both logic 0, the dbctrl bit is ignored. iotst: the iotst bit is used to allow normal microprocessor access to the test registers and control the test mode in each tsb block in the d3mx for board level testing. when iotst is a logic 1, all blocks are held in test mode and the microprocessor may write to a block's test mode 0 registers to manipulate the outputs of the block and consequently the device outputs (refer to the "test mode 0 details" in the "test features" section). hizio, hizdata: the hizio and hizdata bits control the tri-state modes of the d3mx . while the hizio bit is a logic 1, all output pins of the d3mx except the data bus are held in a high-impedance state. the microprocessor interface is still active. while the hizdata bit is a logic 1, the data bus is also held in a high- impedance state which inhibits microprocessor read cycles.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 68 register 08h: master interrupt source #1 bit type function default bit 7 r reg2 0 bit 6 r reg3 0 bit 5 r xfdlint 0 bit 4 r mx23 0 bit 3 r ds3frmr 0 bit 2 r rfdlint 0 bit 1 r rfdleom 0 bit 0 r rboc 0 this register allows software to determine which of the mx23, ds3 frmr, or rboc tsbs produced the interrupt on the intb output pin and whether there are any pending interrupts in the other two interrupt source registers. also, this register reports whether the rfdl or xfdl tsbs have generated interrupts on their respective hdlc controller outputs (i.e. rdlint, rdleom, tdlint, tdludr). these four signals can be configured for active-low, open-drain output and wire-ored together with the intb output to generate a global microprocessor interrupt. reading this register does not remove the interrupt indication; the corresponding tsb's interrupt status register must be read to remove the interrupt indication. rboc: if the rboc bit is a logic 1, the feac rboc tsb is generating an interrupt. register 33h should be read to determine which event in rboc has caused to interrupt. rfdleom: if the rfdleom bit is a logic 1, the rfdl tsb is generating an interrupt due to an end of message occurrence (also visible on the rdleom output when configured for internal hdlc, i.e. rexhdlc=0). rfdlint: if the rfdlint bit is a logic 1, the rfdl tsb is generating an interrupt (also visible on the rdlint output when configured for internal hdlc, i.e. rexhdlc=0).
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 69 ds3frmr: if the ds3frmr bit is a logic 1, the ds3 frmr tsb is generating an interrupt. register 36h should be read to determine which event in ds3 frmr has caused to interrupt. mx23: if the mx23 bit is a logic 1, the mx23 tsb is generating an interrupt due to the detection of a ds2 loopback request. xfdlint: if the xfdlint bit is a logic 1, the xfdl tsb is generating an interrupt (also visible on the tdlint output when configured for internal hdlc, i.e. texhdlc=0). reg2: if the reg2 bit is a logic 1, at least one bit in the master interrupt source #2 register is set, that is, at least one ds2 framer or the xfdl is generating an interrupt. reg3: if the reg3 bit is a logic 1, at least one bit in the master interrupt source #3 register is set, that is, at least one m12 multiplexer is generating an interrupt.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 70 register 09h: master interrupt source #2 bit type function default bit 7 r xfdludr 0 bit 6 r ds2frmr #7 0 bit 5 r ds2frmr #6 0 bit 4 r ds2frmr #5 0 bit 3 r ds2frmr #4 0 bit 2 r ds2frmr #3 0 bit 1 r ds2frmr #2 0 bit 0 r ds2frmr #1 0 this register allows software to determine which of the seven ds2 framer tsbs produced the interrupt on the intb output pin, or whether the xfdl tsb produced an underrun condition. reading this register does not remove the interrupt indication; the corresponding tsb's interrupt status register must be read to remove the interrupt indication. xfdludr: if the xfdludr bit is a logic 1, the xfdl tsb is generating an interrupt due to an underrun of the transmit data buffer (also visible on the tdludr output when configured for internal hdlc, i.e. texhdlc=0).
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 71 register 0ah: master interrupt source #3 bit type function default bit 7 r ds3pmon 0 bit 6 r mx12 #7 0 bit 5 r mx12 #6 0 bit 4 r mx12 #5 0 bit 3 r mx12 #4 0 bit 2 r mx12 #3 0 bit 1 r mx12 #2 0 bit 0 r mx12 #1 0 this register allows software to determine which of the seven mx12 tsbs or the ds3 pmon tsb produced the interrupt on the intb output pin. reading this register does not remove the interrupt indication; the corresponding tsb's interrupt status register must be read to remove the interrupt indication.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 72 register 0ch:ds3 tran configuration bit type function default bit7 r/w cbtran 0 bit6 r/w ais 0 bit5 r/w idl 0 bit4 r/w ferf 0 bit3 r/w sbow 0 bit2 unused x bit1 unused x bit0 r/w cbit 0 cbit: the cbit bit enables the c-bit parity application. when cbit is a logic 1, c- bit parity is enabled, and the associated functions are inserted in the c-bit positions of the incoming ds3 stream. when cbit is a logic 0, the m23 application is selected, and the c-bits are passed transparently through the ds3 tran. sbow: the sbow bit selects whether to insert the bit from the toh input into the stuff opportunity bit or into the f4 bit. when sbow is a logic 1, the bit from the toh input is inserted into the stuff opportunity bit. when sbow is a logic 0, the bit from the toh input is inserted into the f4 bit. ferf: the ferf bit enables transmission of far end receive failure in the outgoing ds3 stream. when ferf is a logic 1, the x1 and x2 overhead bit positions in the ds3 stream are set to logic 0. when ferf is a logic 0, the x1 and x2 overhead bit positions in the ds3 stream are set to logic 1. ais, idl: the ais and idl bits enable the transmission of the alarm indication signal and the idle signal. when ais is a logic 1, the transmit ds3 payload (on the tdat/tpos and tneg outputs) is overwritten with the pattern 1010... when idl is a logic 1, the transmit ds3 payload is overwritten with the pattern 1100...
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 73 cbtran: the cbtran bit controls the c-bits during ais transmission. when cbtran is a logic 0, the c-bits are overwritten with zeros during ais transmission (as is currently specified in ansi t1.107a section 8.1.3.1). the only exception is the network requirement bit, which is forced to the tnr register bit value. when cbtran is a logic 1 and the m23 application is enabled, the c-bits pass through transparently during ais transmission. when cbtran is a logic 1, and the c-bit parity application is enabled, the c-bits are overwritten with the appropriate c-bit parity functions during ais transmission.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 74 register 0dh:ds3 tran diagnostic bit type function default bit7 r/w dlos 0 bit6 r/w dlcv 0 bit5 unused x bit4 r/w dferr 0 bit3 r/w dmerr 0 bit2 r/w dcperr 0 bit1 r/w dperr 0 bit0 r/w dfebe 0 dfebe: the dfebe controls the insertion of far end block errors in the outgoing ds3 stream. when dfebe is set to a logic 1, and the c-bit parity application is enabled, the three c-bits in m-subframe 4 are set to a logic 0. dperr: the dperr controls the insertion of parity errors (p-bit errors) in the outgoing ds3 stream. when dperr is set to a logic 1, the p-bits are inverted before insertion in the ds3 stream. dcperr: the dcperr controls the insertion of c-bit parity errors in the outgoing ds3 stream. when dcperr is set to a logic 1, and the c-bit parity application is enabled, the three c-bits in m-subframe 3 are inverted before insertion in the ds3 stream. dmerr: the dmerr controls the insertion of framing errors (m-bit errors) in the outgoing ds3 stream. when dmerr is set to a logic 1, the m-bits are inverted before insertion in the ds3 stream. dferr: the dferr controls the insertion of framing errors (f-bit errors) in the outgoing ds3 stream. when dferr is set to a logic 1, the f-bits are inverted before insertion in the ds3 stream.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 75 dlcv: the dlcv controls the insertion of a single line code violation in the outgoing ds3 stream. when the dlcv is set to logic 1, a line code violation is inserted by generating an incorrect polarity of violation in the next b3zs signature. the data being transmitted must therefore contain periods of three consecutive zeros in order for the line code violation to be inserted. for example line code violations may not be inserted when transmitting ais, but will be inserted when transmitting the idle signal. this bit is automatically cleared upon insertion of the line code violation. dlos: the dlos controls the insertion of loss of signal in the outgoing ds3 stream. when dlos is set to a logic 1, the data on outputs tpos, tneg, and tdat are forced to continuous zeros. 10.1 ds3 pmon registers latching performance data the ds3 performance monitor (pmon) data registers (16h-1fh) are updated by the rising edge of an internal transfer clock signal. the time between successive rising edges of the transfer clock determines the accumulation interval, which is nominally one second. a microprocessor write to any of the pmon count data registers causes a transfer clock and an update of the pmon data registers. only one register location need be written to cause an update of all pmon data registers. the pmon is loaded with new performance data within 3 rohclk periods of the trailing edge of a microprocessor write. with rohclk at its nominal frequency of 526 khz, the pmon registers should not be read until 6 s have elapsed since the microprocessor write was performed. the data contained in the holding registers are subsequently read from the pmon registers by the microprocessor. the loading is synchronized to the internal event timing so that no events are missed.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 76 register 11h: ds3 pmon interrupt enable/status bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 r/w inte 0 bit 1 r intr 0 bit 0 r ovr 0 ovr: the overrun (ovr) bit indicates the overrun status of the holding registers. a logic 1 in this bit position indicates that a previous interrupt has not been cleared before the end of the next accumulation interval, and that the contents of the holding registers have been overwritten. a logic 0 indicates that no overrun has occurred. this bit is reset to logic 0 when this register is read. intr: the interrupt (intr) bit indicates the current status of the internal interrupt signal. a logic 1 in this bit position indicates that a transfer of counter values to the holding registers has occurred; a logic 0 indicates that no transfer has occurred. the intr bit is set to logic 0 when this register is read. the value of the intr bit is not affected by the value of the inte bit. inte: a logic 1 in the inte bit position enables the ds3 pmon to generate a microprocessor interrupt and assert the intb output when the counter values are transferred to the holding registers. a logic 0 in the inte bit position disables the ds3 pmon from generating an interrupt. when the tsb is reset, the inte bit is set to logic 0, disabling the interrupt. the interrupt is cleared when this register is read.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 77 register 14h: ds3 lcv count lsb bit type function default bit 7 r lcv[7] x bit 6 r lcv[6] x bit 5 r lcv[5] x bit 4 r lcv[4] x bit 3 r lcv[3] x bit 2 r lcv[2] x bit 1 r lcv[1] x bit 0 r lcv[0] x register 15h: ds3 lcv count msb bit type function default bit 7 r lcv[15] x bit 6 r lcv[14] x bit 5 r lcv[13] x bit 4 r lcv[12] x bit 3 r lcv[11] x bit 2 r lcv[10] x bit 1 r lcv[9] x bit 0 r lcv[8] x these registers indicate the number of ds3 line code violation (lcv) events that occurred during the previous accumulation interval. a transfer operation of all counter registers within the selected pmon can be triggered by writing to either lcv count register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 78 register 16h: ds3 ferr count lsb bit type function default bit 7 r ferr[7] x bit 6 r ferr[6] x bit 5 r ferr[5] x bit 4 r ferr[4] x bit 3 r ferr[3] x bit 2 r ferr[2] x bit 1 r ferr[1] x bit 0 r ferr[0] x register 17h: ds3 ferr count msb bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 unused x bit 1 r ferr[9] x bit 0 r ferr[8] x these registers indicate the number of ds3 framing error (ferr) events that occurred during the previous accumulation interval. a transfer operation of all counter registers within the selected pmon can be triggered by writing to either ferr count register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 79 register 18h: ds3 exzs count lsb bit type function default bit 7 r exzs[7] x bit 6 r exzs[6] x bit 5 r exzs[5] x bit 4 r exzs[4] x bit 3 r exzs[3] x bit 2 r exzs[2] x bit 1 r exzs[1] x bit 0 r exzs[0] x register 19h: ds3 exzs count msb bit type function default bit 7 r exzs[15] x bit 6 r exzs[14] x bit 5 r exzs[13] x bit 4 r exzs[12] x bit 3 r exzs[11] x bit 2 r exzs[10] x bit 1 r exzs[9] x bit 0 r exzs[8] x these registers indicate the number of summed excessive zeros (exzs) that occurred during the previous accumulation interval. one or more excessive zeros occurrences within an 85 bit block is counted as one summed excessive zero. a transfer operation of all counter registers within the selected pmon can be triggered by writing to either exzs count register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 80 register 1ah: ds3 perr count lsb bit type function default bit 7 r perr[7] x bit 6 r perr[6] x bit 5 r perr[5] x bit 4 r perr[4] x bit 3 r perr[3] x bit 2 r perr[2] x bit 1 r perr[1] x bit 0 r perr[0] x register 1bh: ds3 perr count msb bit type function default bit 7 unused x bit 6 unused x bit 5 r perr[13] x bit 4 r perr[12] x bit 3 r perr[11] x bit 2 r perr[10] x bit 1 r perr[9] x bit 0 r perr[8] x these registers indicate the number of p-bit parity error (perr) events that occurred during the previous accumulation interval. a transfer operation of all counter registers within the selected pmon can be triggered by writing to either perr count register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 81 register 1ch: ds3 cperr count lsb bit type function default bit 7 r cperr[7] x bit 6 r cperr[6] x bit 5 r cperr[5] x bit 4 r cperr[4] x bit 3 r cperr[3] x bit 2 r cperr[2] x bit 1 r cperr[1] x bit 0 r cperr[0] x register 1dh: ds3 cperr count msb bit type function default bit 7 unused x bit 6 unused x bit 5 r cperr[13] x bit 4 r cperr[12] x bit 3 r cperr[11] x bit 2 r cperr[10] x bit 1 r cperr[9] x bit 0 r cperr[8] x these registers indicate the number of c-bit parity error (cperr) events that occurred during the previous accumulation interval. a transfer operation of all counter registers within the selected pmon can be triggered by writing to either cperr count register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 82 register 1eh: ds3 febe count lsb bit type function default bit 7 r febe[7] x bit 6 r febe[6] x bit 5 r febe[5] x bit 4 r febe[4] x bit 3 r febe[3] x bit 2 r febe[2] x bit 1 r febe[1] x bit 0 r febe[0] x register 1fh: ds3 febe count msb bit type function default bit 7 unused x bit 6 unused x bit 5 r febe[13] x bit 4 r febe[12] x bit 3 r febe[11] x bit 2 r febe[10] x bit 1 r febe[9] x bit 0 r febe[8] x these registers indicate the number of far end block error (febe) events that occurred during the previous accumulation interval. a transfer operation of all counter registers within the selected pmon can be triggered by writing to either febe count register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 83 register 20h: xfdl tsb configuration bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 r/w eom 0 bit 3 r/w inte 0 bit 2 r/w abt 0 bit 1 r/w crc 0 bit 0 r/w en 0 en: the enable bit (en) controls the overall operation of the xfdl tsb. when the en bit is set to a logic 1, the xdfl tsb is enabled and flag sequences are sent until data is written into the transmit data register. when the en bit is set to logic 0, the xfdl tsb is disabled. crc: the crc enable bit controls the generation of the ccitt-crc frame check sequence (fcs). setting the crc bit to logic 1 enables the ccitt-crc generator and the appends the 16 bit fcs to the end of each message. when the crc bit is set to logic 0, the fcs is not appended to the end of the message. the crc type used is the ccitt-crc with generator polynomial = x 16 + x 12 +x 5 + 1. the high order bit of the fcs word is transmitted first. abt: the abort (abt) bit controls the sending of the 7 consecutive ones hdlc abort code. setting the abt bit to a logic 1 causes the 11111110 code to be transmitted after the last byte from the transmit data register is transmitted. aborts are continuously sent until this bit is reset to a logic 0. inte: the inte bit enables the generation of an interrupt via the tdlint output. setting the inte bit to logic 1 enables the generation of an interrupt by asserting the tdlint output; setting inte to logic 0 disables the generation of an interrupt.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 84 eom: the eom bit indicates that the last byte of data written in the transmit data register is the end of the present data packet. if the crc bit is set then the 16-bit fcs word is appended to the last data byte transmitted and a continuous stream of flags is generated. the eom bit is automatically cleared before transmission of the next data packet begins. the eom register bit value can also be set to logic 1 by pulsing the tdleomi input pin.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 85 register 21h: xfdl tsb interrupt status bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 unused x bit 1 r int 0 bit 0 r/w udr 0 int: the int bit indicates when the xfdl tsb is ready to accept a new data byte for transmission. the int bit is set to a logic 1 when the previous byte in the transmit data register has been loaded into the parallel to serial converter and a new byte can be written into the transmit data register. the int bit is set to a logic 0 while new data is in the transmit data register. the int bit is not disabled by the inte bit in the configuration register. udr: the udr bit indicates when the xfdl tsb has underrun the data in the transmit data register. the udr bit is set to a logic 1 if the parallel to serial conversion of the last byte in the transmit data register has completed before the new byte was written into the transmit data register. once an underrun has occurred, the xfdl transmits an abort, followed by a flag, and waits to transmit the next valid data byte. if the udr bit is still set after the transmission of the flag the xfdl will continuously transmit the all-ones idle pattern. the udr bit can only be cleared by writing a logic 0 to the udr bit position in this register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 86 register 22h: xfdl tsb transmit data bit type function default bit 7 r/w td7 x bit 6 r/w td6 x bit 5 r/w td5 x bit 4 r/w td4 x bit 3 r/w td3 x bit 2 r/w td2 x bit 1 r/w td1 x bit 0 r/w td0 x data written to this register is serialized and transmitted on the path maintenance data link least significant bit first. the xfdl tsb signals when the next data byte is required by asserting the tdlint output (if enabled) and by setting the int bit in the status register high. when int and/or tdlint is set, the transmit data register must be written with the next message byte within 4 data bit periods to prevent the occurrence of an underrun. at a nominal 28.2 kbit/sec link data rate the required write interval is 110sec.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 87 register 24h: rfdl tsb configuration bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 unused x bit 1 r/w tr 0 bit 0 r/w en 0 en: the enable bit (en) controls the overall operation of the rfdl tsb. when set, the rdfl tsb is enabled; when reset the rfdl tsb is disabled. when the tsb is disabled, the fifo and interrupts are all cleared, however, the programming of the interrupt control/status register is not affected. when the tsb is enabled, it will immediately begin looking for flags. setting the terminate reception bit (tr) forces the rfdl tsb to immediately terminate the reception of the current lapd frame, empty the fifo, clear the interrupts, and begin searching for a new flag sequence. the rfdl handles the tr input in the same manner as if the en bit had been cleared and then set. the tr bit in the configuration register will reset itself after a rising and falling edge have occurred on the clk input to the rfdl tsb once the write to this register has completed and web goes inactive. if the configuration register is read after this time, the tr bit value returned will be zero. the rfdl tsb handles the tr input in the same manner as clearing and setting the en bit, therefore, the rfdl state machine will begin searching for flags and an interrupt will be generated when the first flag is detected.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 88 register 25h: rfdl tsb interrupt control/status bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 r/w intc1 0 bit 1 r/w intc0 0 bit 0 r int 0 intc1, intc0: the intc1 and intc0 bits control when an interrupt is asserted based on the number of received data bytes in the fifo as follows: intc1 intc0 description 0 0 disable interrupts (all sources) 0 1 enable interrupt when fifo receives data 1 0 enable interrupt when fifo has 2 bytes of data 1 1 enable interrupt when fifo has 3 bytes of data int: the int bit reflects the status of the external rdlint interrupt unless the intc1 and intc0 bits are set to disable interrupts. in that case, the rdlint output is forced to 0 and the int bit of the interrupt control/status register will reflect the state of the internal interrupt latch. fifo: in addition to the fifo fill status, interrupts are also generated for eom (end of message), ovr (fifo overrun), detection of the abort sequence while not
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 89 receiving all ones and on detection of the first flag while receiving all ones. the interrupt is reset by a receive data register read that empties the fifo, unless the cause of the interrupt was due to a fifo overrun. the interrupt due to a fifo overrun is cleared on a status register read, by disabling the tsb, or by setting tr high. the contents of the interrupt control/status register should only be changed when the rfdl tsb is disabled to prevent any erroneous interrupt generation.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 90 register 26h: rfdl tsb status bit type function default bit 7 r fe x bit 6 r ovr x bit 5 r flg x bit 4 r eom x bit 3 r crc x bit 2 r nvb2 x bit 1 r nvb1 x bit 0 r nvb0 x nvb[2:0] the nvb[2:0] bit positions indicate the number of valid bits in the receive data register byte. it is possible that not all of the bits in the receive data register are valid when the last data byte is read since the data frame can be any number of bits in length and not necessarily an integral number of bytes. the receive data register is filled from the msb to the lsb bit position, with one to eight data bits being valid. the number of valid bits is equal to 1 plus the value of nvb[2:0]. a nvb[2:0] value of 000 binary indicates that only the msb in the register is valid. nvb[2:0] is only valid when the eom bit is a logic 1 and the flg bit is a logic 1 and the ovr bit is a logic 0. crc: the crc bit is set if a crc error was detected in the last received lapd frame. the crc bit is only valid when eom is logic 1 and flg is a logic 1 and ovr is a logic 0. on an interrupt generated from the detection of first flag, reading the status register will return invalid nvb[2:0] and crc bits, even though the eom bit is logic 1 and the flg bit is logic 1. eom: the end of message bit (eom) follows the rdleom output. it is set when: 1. the last byte in the lapd frame (eom) is being read from the receive data register,
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 91 2. an abort sequence is detected while not in the receiving all-ones state and the byte, written to the fifo due to the detection of the abort sequence, is being read from the fifo, 3. the first flag has been detected and the dummy byte, written into the fifo when the rfdl changes from the receiving all-ones state to the receiving flags state, is being read from the fifo, 4. immediately on detection of fifo overrun. the eom bit is passed through the fifo with the data so that the status will correspond to the data just read from the fifo. flg: the flag bit (flg) is set if the rfdl tsb has detected the presence of the lapd flag sequence (01111110) in the data. flg is reset only when the lapd abort sequence (01111111) is detected in the data or when the rfdl tsb is disabled. this bit is passed through the fifo with the data so that the status will correspond to the data just read from the fifo. the reception of bit-oriented codes over the data link will also force an abort due to its eight ones pattern. ovr: the receiver overrun bit (ovr) is set when data is written over unread data in the fifo. this bit is not reset until after the status register is read. while ovr is high, the rfdl and fifo are held in the reset state, causing the flg and eom bits in the status register to be reset also. fe: the fifo empty bit (fe) is high when the last fifo entry is read and goes low when the fifo is loaded with new data. if the receive data register is read while there is no valid data, then a fifo underrun condition occurs. the underrun condition is reflected in the status register by forcing all bits to logic zero on the first status register read immediately following the received data register read which caused the underrun condition.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 92 register 27h: rfdl tsb receive data bit type function default bit 7 r rd7 x bit 6 r rd6 x bit 5 r rd5 x bit 4 r rd4 x bit 3 r rd3 x bit 2 r rd2 x bit 1 r rd1 x bit 0 r rd0 x rd0 rd0 corresponds to the first bit of the serial byte received by the rfdl. this register is actually a 4 level fifo. if data is available, the fe bit in the status register is low. if intc[1:0] (in the enable/status register) is set to 01, the receive data register must be read within 31 data bit periods to prevent an overrun. if intc[1:0] is set to 11 the receiver data register must be read within 15 data bit periods. when an overrun is detected, an interrupt is generated and the fifo is held cleared until the status register is read. when the lapd abort sequence (01111111) is detected in the data an abort interrupt is generated and the data that has been shifted into the serial to parallel converter is written into the fifo. a read of the receive data register increments the fifo pointer at the end of the read. if the receive data register read causes an fifo underrun, then the pointer is inhibited from incrementing. the underrun condition will be signaled in the next status read by returning all zeros.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 93 register 28h: mx23 configuration bit type function default bit7 unused x bit6 unused x bit5 unused x bit4 unused x bit3 r/w lbcode[1] 0 bit2 r/w lbcode[0] 0 bit1 r/w cbe 0 bit0 r/w inte 0 inte: when set high, the inte bit enables the mx23 to activate the interrupt output, intb, whenever any of the lbri[7:1] bits are set high in the mx23 loopback request interrupt register. mx23 interrupts are masked when inte is cleared low. cbe: when set high, the cbe bit enables c-bit parity operation. when cbe is low, m23 operation is enabled. while in c-bit parity mode, loopback request detection and loopback request insertion are disabled. the generated ds2 clock, gd2clk, is nominally 6.3062723 mhz while in c-bit parity mode, received c bits are ignored, and transmitted c bits are set to 1. while in m23 mode, the generated ds2 clock, gd2clk, is nominally 6.311993 mhz and c bit decoding and encoding is fully operational. lbcode[1:0]: the lbcode[1:0] bits select the valid state for a loopback request coded in the c-bits of the ds3 signals. transmit and receive are not independent; the same code is expected in the receive ds3 as is inserted in the transmitted ds3. the following table gives the correspondence between lbcode[1:0] bits and the valid codes:
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 94 lbcode[1:0] loopback code 00 c1 = c2 and c1 = c3 01 c1 = c3 and c1 = c2 10 c2 = c3 and c1 = c2 11 c1 = c2 and c1 = c3 if lbcode[1:0] is 'b00 or 'b11, the loopback code is as per ansi t1.107a section 8.2.1 and tr-tsy-000009 section 3.7. because tr-tsy-000233 section 5.3.14.1 recommends compatibility with non-compliant existing equipment, the two other loopback command possibilities are also supported. lbcode[1:0]: the lbcode[1:0] bits become logical 0 upon either a hardware or software reset.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 95 register 29h: mx23 demux ais insert register bit type function default bit7 unused x bit6 r/w dais[7] 0 bit5 r/w dais[6] 0 bit4 r/w dais[5] 0 bit3 r/w dais[4] 0 bit2 r/w dais[3] 0 bit1 r/w dais[2] 0 bit0 r/w dais[1] 0 dais[7:1]: setting any of the dais[7:1] bits activates insertion of the alarm indication signal (all ones) into the corresponding ds2 stream demultiplexed from the ds3 signal input on rdat. demux ais insertion takes place after the point where per ds2 loopback may be invoked using the loopback activate register thus allowing demux ais to be inserted into the through path while a ds2 loopback is activated, if desired.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 96 register 2ah: mx23 mux ais insert register bit type function default bit7 unused x bit6 r/w mais[7] 0 bit5 r/w mais[6] 0 bit4 r/w mais[5] 0 bit3 r/w mais[4] 0 bit2 r/w mais[3] 0 bit1 r/w mais[2] 0 bit0 r/w mais[1] 0 mais[7:1]: setting any of the mais[7:1] bits activates insertion of the alarm indication signal (all ones) into the corresponding ds2 stream multiplexed into the ds3 signal output on tdat. mux ais insertion takes place before the point where per ds2 loopback may be invoked using the loopback activate register and thus mux ais cannot be inserted while a ds2 loopback is activated.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 97 register 2bh: mx23 loopback activate register bit type function default bit7 unused x bit6 r/w lba[7] 0 bit5 r/w lba[6] 0 bit4 r/w lba[5] 0 bit3 r/w lba[4] 0 bit2 r/w lba[3] 0 bit1 r/w lba[2] 0 bit0 r/w lba[1] 0 lba[7:1]: setting any of the lba[7:1] bits activates loopback of the corresponding ds2 stream from the input ds3 signal to the output ds3 signal. the demultiplexed ds2 signals continue to present valid payloads while loopbacks are activated. the mx23 demux ais insert register allows insertion of ds2 ais if required.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 98 register 2ch: mx23 loopback request insert register bit type function default bit7 unused x bit6 r/w ilbr[7] 0 bit5 r/w ilbr[6] 0 bit4 r/w ilbr[5] 0 bit3 r/w ilbr[4] 0 bit2 r/w ilbr[3] 0 bit1 r/w ilbr[2] 0 bit0 r/w ilbr[1] 0 ilbr[7:1]: setting any of the ilbr[7:1] bits enables the insertion of a loopback request in the corresponding ds2 stream in the output ds3 signal. the format of the loopback request is determined by the lbcode[1:0] bits in the mx23 configuration register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 99 register 2dh: mx23 loopback request detect register bit type function default bit7 unused x bit6 r lbrd[7] x bit5 r lbrd[6] x bit4 r lbrd[5] x bit3 r lbrd[4] x bit2 r lbrd[3] x bit1 r lbrd[2] x bit0 r lbrd[1] x lbrd[7:1] the lbrd[7:1] bits are set high while a loopback request is detected for the corresponding ds2 stream in the input ds3 signal. the lbrd[7:1] bits are set low otherwise. the format of the loopback request expected is determined by the lbcode[1:0] bits in the mx23 configuration register. as per tr-tsy- 000009 section 3.7, the loopback request must be present for five successive m-frames before declaration of detection. removal of the loopback request is declared when it has been absent for five successive m-frames.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 100 register 2eh: mx23 loopback request interrupt register bit type function default bit7 unused x bit6 r lbri[7] x bit5 r lbri[6] x bit4 r lbri[5] x bit3 r lbri[4] x bit2 r lbri[3] x bit1 r lbri[2] x bit0 r lbri[1] x lbri[7:1]: the lbri[7:1] bits are set high when a loopback request is asserted or deasserted for the corresponding ds2 stream in the input ds3 signal. the lbri[7:1] bits are set high whenever the corresponding lbrd[7:1] bits change state. if interrupts are enabled using the inte bit in the configuration register then the interrupt output, intb, is activated. the lbri[7:1] bits are to logic 0 immediately following a read of the register, acknowledging the interrupt and deactivating the intb output.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 101 register 31h: feac xboc tsb code bit type function default bit 7 unused x bit 6 unused x bit 5 r/w bc[5] 1 bit 4 r/w bc[4] 1 bit 3 r/w bc[3] 1 bit 2 r/w bc[2] 1 bit 1 r/w bc[1] 1 bit 0 r/w bc[0] 1 this register enables the xboc tsb to generate a bit oriented code and selects the 6-bit code to be transmitted. when this register is written with any 6-bit code other than 111111, that code will be transmitted repeatedly in the far-end alarm and control (feac) channel with the format 111111110[bc0][bc1][bc2][bc3][bc4][bc5]0. when the register is written with 111111, the xboc tsb is disabled.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 102 register 32h: rboc configuration/interrupt enable bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 r/w idle 0 bit 1 r/w avc 0 bit 0 r/w boce 0 this register selects the validation criteria to be used in determining a valid bit-oriented code (boc) on the far-end alarm and control (feac) channel and enables generation of an interrupt at code validation. boce: the boce bit position enables or disables the generation of an interrupt when a valid boc is detected. a logic 1 in this bit position enables generation of an interrupt; a logic 0 in this bit position disables interrupt generation. when the d3mx is reset, boce is reset to logic 0; therefore, interrupt generation is disabled. avc: the avc bit position selects the validation criterion used in determining a valid boc. a logic 0 selects the 8 out of 10 matching boc criterion; a logic 1 in the avc bit position selects the "alternative" validation criterion of 4 out of 5 matching bocs. idle: the idle bit position enables or disables the generation of an interrupt when there is a transition from a validated boc to idle code. a logic 1 in this bit position enables generation of an interrupt; a logic 0 in this bit position disables interrupt generation.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 103 register 33h: rboc interrupt status bit type function default bit 7 r idlei x bit 6 r boci x bit 5 r boc[5] x bit 4 r boc[4] x bit 3 r boc[3] x bit 2 r boc[2] x bit 1 r boc[1] x bit 0 r boc[0] x boc[5:0] the bit positions boc[5:0] contain the received bit-oriented codes. a logic 1 in the boci bit position indicates that a validated boc code has generated an interrupt; a logic 0 in the boci bit position indicates that no boc has been detected. since the bit-oriented code "111111" is not recognized by the rboc, the boc[5:0] bits are set to all ones ("111111") if no valid code has been detected. the boci bit position is cleared to logic 0 and the interrupt is deasserted when this register is read. idlei: the idlei bit position indicates whether an interrupt was generated by the detection of the transition from a valid boc to idle code. a logic 1 in the idlei bit position indicates that a transition from a valid boc to idle code has generated an interrupt; a logic 0 in the idlei bit position indicates that no transition from a valid boc to idle code has been detected. idlei is cleared to logic 0 when the register is read. register 34h: ds3 frmr configuration bit type function default bit7 r/w aispat 1 bit6 r/w fdet 0 bit5 r/w mbdis 0
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 104 bit type function default bit4 r/w m3o8 0 bit3 r/w uni 0 bit2 r/w refr 0 bit1 r/w aisc 0 bit0 r/w cbe 0 cbe: the cbe bit selects whether the c-bit parity application is enabled. when a logic 1 is written to cbe, c-bit parity mode is enabled. when a logic 0 is written, c-bit parity mode is disabled. aisc: the aisc bit controls the algorithm used to detect the alarm indication signal (ais). when a logic 1 is written to aisc, the algorithm checks that a framed ds3 signal with all c-bits set to logic 0 is observed for a period of time before declaring ais. the payload contents are checked to the pattern selected by the aispat bit. when a logic 0 is written to aisc, the ais detection algorithm is determined solely by the settings of aispat and aisones register bits (see bit mapping table in the additional configuration register description). refr: the refr bit is used to trigger reframing. if a logic 1 is written to refr when it was previously logic 0, the frmr is forced out-of-frame, and a new search for frame alignment is initiated. note that only a low to high transition of the refr bit triggers reframing; multiple write operations are required to ensure such a transition. uni: the uni bit is used to configure the frmr to accept either unipolar or bipolar data streams. when a logic 1 is written to uni, the frmr accepts unipolar data and line code violation indication on its inputs. when a logic 0 is written to uni, the frmr accepts bipolar data on its inputs and performs b3zs decoding and line code violation reporting.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 105 m3o8: the m3o8 bit configures the out of frame decision criteria. if m3o8 is a logic 1, out of frame is declared if at least 3 of 8 framing bits are in error. if m3o8 is a logic 0, the standard 3 of 16 bits in error criteria is used. mbdis: the mbdis bit disables the use of m-bit errors as a criteria for losing frame alignment. when mbdis is set to logic 1, m-bit errors are disabled from causing an oof; the loss of frame criteria is based solely on the number of f- bit errors selected by the m3o8 bit. when mbdis is set to logic 0, errors in either m-bits or f-bits are enabled to cause an oof. when mbdis is logic 0, an oof can occur when one or more m-bit errors occur in 3 out of 4 consecutive m-frames, or when the f-bit error ratio selected by the m3o8 bit. is exceeded. fdet: the fdet bit selects the fast detection timing for ais, idle and red. when fdet is set to logic 1, the ais, idle, and red detection time is 2.23 ms; when fdet is set to logic 0, the detection time is 13.5 ms. aispat: the aispat bit controls the pattern used to detect the alarm indication signal (ais). when a logic 1 is written to aispat, the ais detection algorithm checks that a framed ds3 signal containing the repeating pattern 1010... is present. the c-bits are checked for the value specified by the aisc bit setting. when a logic 0 is written to aispat, the ais detection algorithm is determined solely by the settings of aisc and aisones register bits (see bit mapping table in the additional configuration register description).
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 106 register 35h: ds3 frmr interrupt enable (ace=0) bit type function default bit7 r/w cofae 0 bit6 r/w rede 0 bit5 r/w cbite 0 bit4 r/w ferfe 0 bit3 r/w idle 0 bit2 r/w aise 0 bit1 r/w oofe 0 bit0 r/w lose 0 lose: the lose bit enables an interrupt to be generated when a change of state of the loss of signal detector occurs. the state of the detector is visible in the losv bit position in the ds3 frmr status register and on the rlos pin. when lose is set to logic 1, the interrupt output, intb, is set low when the state of the los indication changes. oofe: the oofe bit enables an interrupt to be generated when a change of state of the ds3 frmr frame alignment acquisition circuitry occurs. the state of the frame alignment acquisition circuitry is visible in the oofv bit location in the ds3 frmr status register and on the roof/rred pin when the redo bit in the master alarm enable register is logic 0. when the circuitry has lost frame alignment and is searching for the new alignment, an out of frame is indicated and the oofv bit and roof pin are set to logic 1. when the circuitry has found frame alignment, the oofv bit and roof pin are set to logic 0. when oofe is set to logic 1, the interrupt output, intb, is set low when the state of the oof indication changes. aise: the aise bit enables an interrupt to be generated when a change of state of the ds3 ais signal detector occurs. the state of the ais detector is visible in the aisv bit location in the ds3 frmr status register and on the rais pin. when aise is set to logic 1, the interrupt output, intb, is set low when the state of the ais detector changes.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 107 idle: the idle bit enables an interrupt to be generated when a change of state of the ds3 idle signal detector occurs. when idle is set to logic 1, the interrupt output, intb, is set low when the state of the idle detector changes. ferfe: the ferfe bit enables an interrupt to be generated when a change of state of the ferf indication occurs. the ferf indication is visible in the ferfv bit location of the ds3 frmr status register and on the rferf pin. when ferfe is set to logic 1, the interrupt output, intb, is set low when the state of the ferf output changes. cbite: the cbite bit enables an interrupt to be generated when change of state in the c-bit identification indication internal to the ds3 frmr occurs. when cbite is set to logic 1, the interrupt output, intb, is set low when the state of the c-bit identification indication changes. rede: the rede bit enables an interrupt to be generated when a change of state of the ds3 red indication occurs. the ds3 red indication is visible in the redv bit location of the ds3 frmr status register and on the roof/rred pin when the redo bit in the master alarm enable register ( register 06hex) is set to logic 1. when rede is set to logic 1, the interrupt output, intb, is set low when the state of the red indication changes. cofae: the cofae bit enables an interrupt to be generated when a change of frame alignment (i.e. a cofa event ) occurs. when cofae is set to logic 1, the interrupt output, intb, is set low when the cofa event occurs. a frmr-generated interrupt is cleared when the frmr interrupt status register is read.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 108 register 35h: ds3 frmr additional configuration register (ace=1) bit type function default bit7 unused x bit6 unused x bit5 r/w aisones 0 bit4 r/w bpvo 0 bit3 r/w exzso 0 bit2 r/w exzdet 0 bit1 r/w salgo 0 bit0 r/w dalgo 0 dalgo: the dalgo bit determines the criteria used to decode a valid b3zs signature. when dalgo is set to logic 1, a valid b3zs signature is declared and 3 zeros substituted whenever a zero followed by a bipolar violation of the opposite polarity to the last observed bpv is seen. when the dalgo bit is set to logic 0, a valid b3zs signature is declared and the 3 zeros are substituted whenever a zero followed by a bipolar violation is observed. salgo: the salgo bit determines the criteria used to establish a valid b3zs signature used to map bpvs to line code violation indications. any bpv that is not part of a valid b3zs signature is indicated as an lcv. when the salgo bit is set to logic 1, a valid b3zs signature is declared whenever a zero followed by a bipolar violation is observed. when salgo is set to logic 0, a valid b3zs signature is declared whenever a zero followed by a bipolar violation of the opposite polarity to the last observed bpv is seen. exzdet: the exzdet bit determines the type of zero occurrences to be included in the lcv indication. when exzdet is set to logic 1, the occurrence of an excessive zero generates a single pulse indication that is used to indicate an lcv. when exzdet is set to logic 0, every occurrence of 3 consecutive zeros generates a pulse indication that is used to indicate an lcv. for example, if a sequence of 15 consecutive zeros were received, with exzdet=1 only a single lcv would be indicated for this string of excessive zeros; with
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 109 exzdet=0, five lcvs would be indicated for this string (i.e. one lcv for every 3 consecutive zeros). exzso: the exzso bit enables only summed zero occurrences to be accumulated in the pmon exzs count registers. when exzso is set to logic 1, any excessive zeros occurrences over an 85 bit period increments the pmon exzs counter by one. when exzso is set to logic 0, summed lcvs are accumulated in the pmon exzs count registers. a summed lcv is defined as the occurrence of either bpvs not part of a valid b3zs signature or 3 consecutive zeros (or excessive zeros if exzdet=1) occurring over an 85 bit period; each summed lcv occurrence increment the pmon exzs counter by one. bpvo: the bpvo bit enables only bipolar violations to indicate line code violations and be accumulated in the pmon lcv count registers. when bpvo is set to logic 1, only bpvs not part of a valid b3zs signature generate an lcv indication and increment the pmon lcv counter. when bpvo is set to logic 0, both bpvs not part of a valid b3zs signature, and either 3 consecutive zeros or excessive zeros generate an lcv indication and increment the pmon lcv counter. aisones: the aisones bit controls the pattern used to detect the alarm indication signal (ais) when both aispat and aisc bits in ds3 frmr configuration register (34h) are logic 0; if either aispat or aisc are logic 1, the aisones bit is ignored. when a logic 0 is written to aisones, the algorithm checks that a framed all-ones payload pattern (1111...) signal is observed for a period of time before declaring ais. only the payload bits are observed to follow an all-ones pattern, the overhead bits (x, p, m, f, c) are ignored. when a logic 1 is written to aisones, the algorithm checks that an unframed all- ones pattern (1111...) signal is observed for a period of time before declaring ais. in this case all the bits, including the overhead, are observed to follow an all-ones pattern. the valid combinations of aispat, aisc, and aisones bits are summarized below:
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 110 aispat aisc aisones ais detected 1 0 x framed ds3 stream containing repeating 1010 pattern; overhead bits ignored. 0 1 x framed ds3 stream containing c-bits all logic 0; payload bits ignored. 1 1 x framed ds3 stream containing repeating 1010 pattern and c-bits all logic 0. 0 0 0 framed ds3 stream containing all-ones payload pattern; overhead bits ignored. 0 0 1 unframed all-ones ds3 stream.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 111 register 36h: ds3 frmr interrupt status bit type function default bit 7 r cofai x bit 6 r redi x bit 5 r cbiti x bit 4 r ferfi x bit 3 r idli x bit 2 r aisi x bit 1 r oofi x bit 0 r losi x losi: the losi bit indicates that a change of state of the loss of signal detector has occurred. the state of the detector is visible in the losv bit position in the ds3 frmr status register and on the rlos pin. when the losi bit is a logic 1, a change in the los state has occurred. when the losi bit is logic 0, no change in the los state has occurred. oofi: the oofi bit indicates that a change of state of the ds3 frmr frame alignment acquisition circuitry has occurred. the state of the frame alignment acquisition circuitry is visible in the oofv bit location in the ds3 frmr status register and on the roof/rred pin when the redo bit in the master alarm enable register is logic 0. when the circuitry has lost frame alignment and is searching for the new alignment, an out of frame is indicated and the oofv bit and roof pin are set to logic 1. when the circuitry has found frame alignment, the oofv bit and roof pin are set to logic 0. when the oofi bit is a logic 1, a change in the oof state has occurred. when the oofi bit is logic 0, no change in the oof state has occurred. aisi: the aisi bit indicates that a change of state of the ds3 ais signal detector has occurred. the state of the ais detector is visible in the aisv bit location in the ds3 frmr status register and on the rais pin. when the aisi bit is a logic 1, a change in the ais detector state has occurred. when the aisi bit is logic 0, no change in the ais detector state has occurred.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 112 idli: the idli bit indicates that a change of state of the ds3 idle signal detector has occurred. when the idli bit is a logic 1, a change in the idle detector state has occurred. when the idli bit is logic 0, no change in the idle signal detector state has occurred. ferfi: the ferfi bit indicates that a change of state of the ferf indication has occurred. the ferf indication is visible in the ferfv bit location of the ds3 frmr status register and on the rferf pin. when the ferfi bit is a logic 1, a change in the ferf state has occurred. when the ferfi bit is logic 0, no change in the ferf state has occurred. cbiti: the cbiti bit indicates that a change of state in the c-bit identification indication internal to the ds3 frmr has occurred. when the cbiti bit is a logic 1, a change in the internal cbit state has occurred. when the cbiti bit is logic 0, no change in the cbit state has occurred. redi: the redi bit indicates that a change of state of the ds3 red indication has occurred. the ds3 red indication is visible in the redv bit location of the ds3 frmr status register and on the roof/rred pin when the redo bit in the master alarm enable register ( register 06hex) is set to logic 1. when the redi bit is a logic 1, a change in the red state has occurred. when the redi bit is logic 0, no change in the red state has occurred. cofai: the cofai bit indicates that a change of frame alignment (i.e. a cofa event) has occurred. when the cofai bit is a logic 1, the frame alignment acquisition circuitry has detected that the new alignment differs from the previous frame alignment. when the cofai bit is logic 0, there was no difference from the current frame alignment and the previous frame alignment. the interrupt status bits are cleared when the frmr interrupt status register is read.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 113 register 37h: ds3 frmr status bit type function default bit 7 r/w ace 0 bit 6 r redv x bit 5 r cbitv x bit 4 r ferfv x bit 3 r idlv x bit 2 r aisv x bit 1 r oofv x bit 0 r losv x losv: the losv bit indicates the current state of the loss of signal detector. when the losv bit is a logic 1, a sequence of 175 consecutive zeros was detected on the dual-rail rpos and rneg ds3 inputs. when the losv bit is logic 0, a valid ds3 signal with a ones' density greater than 33% for 175 1 bit periods was detected on the dual-rail inputs. oofv: the oofv bit indicates the current state of the ds3 frmr frame alignment acquisition circuitry. when the circuitry has lost frame alignment and is searching for the new alignment, an out of frame is indicated and the oofv bit is set to logic 1. when the circuitry has found frame alignment, the oofv bit is set to logic 0. aisv: the aisv bit indicates the current state of the ds3 ais signal detector. when the aisv bit is a logic 1, the ds3 ais pattern has been received for 2.23ms (or for 13.5ms when fdet is logic 0). when the aisv bit is logic 0, the ds3 ais pattern has not been received for either 2.23ms or 13.5ms. idlv: the idlv bit indicates the current state of the ds3 idle signal detector. when the idlv bit is a logic 1, the ds3 idle pattern has been received for 2.23ms (or for 13.5ms when fdet is logic 0). when the idlv bit is logic 0, the ds3 idle pattern has not been received for either 2.23ms or 13.5ms.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 114 the ferfv bit indicates the current state of the ferf indication. when the ferfv bit is a logic 1, the frmr detected that the second to last m-frame's x2=x1=0. when the ferfv bit is logic 0, the second to last m-frame's x2=x1=1. cbitv: the cbitv bit indicates the current state in the c-bit identification indication. when the cbitv bit is a logic 1, the first c-bit of m sub-frame 1 has been observed to be logic 1 for 63 consecutive occasions. when the cbitv bit is logic 0, the first c-bit of sub-frame 1 has either not been logic 1 for 63 consecutive occasions or, if cbitv was previously logic 1, the first c-bit of sub-frame 1 has been observed to be logic 0 for 2 or more times within 15 consecutive occasions. redv: the redv bit indicates the current state of the ds3 red indication. when the redv bit is a logic 1, the ds3 frmr frame alignment acquisition circuitry has been out of frame for 2.23ms (or for 13.5ms when fdet is logic 0). when the redv bit is logic 0, the frame alignment circuitry has found frame (i.e. oofv=0) for 2.23ms ( or 13.5ms if fdet=0). ace: the ace bit selects the additional configuration register. this register is located at address 35h, and is only accessible when the ace bit is set to logic 1. when ace is set to logic 0, the interrupt enable register is accessible at address 35h.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 115 registers 40h, 50h, 60h, 70h, 80h, 90h and a0h: ds2 frmr configuration bit type function default bit7 r/w g747 0 bit6 unused x bit5 r/w word 0 bit4 r/w m2o5 0 bit3 r/w mbdis 0 bit2 r/w refr 0 bit1 unused x bit0 unused x refr: the refr bit is used to trigger reframing. if a logic 1 is written to refr when it was previously logic 0, the frmr is forced out-of-frame, and a new search for frame alignment is initiated. note that only a low-to-high transition of the refr bit triggers reframing; multiple write operations are required to ensure such a transition. mbdis: the mbdis bit disables the declaration of out-of-frame upon excessive m-bit errors. if mbdis is a logic 0, out-of-frame is declared when one or more m- bit errors are detected in 3 out of 4 consecutive m-frames. if mbdis is a logic 1, the state of the m-bits is ignored once in frame. regardless of the state of the mbdis bit, the f-bits are always monitored for invalid framing. m2o5: the m2o5 bit selects the error ratio for declaring out-of-frame (oof) when in ds2 mode only. when a 1 is written to m2o5, the framer declares oof when 2 f-bit errors out of 5 consecutive f-bits are observed. when a 0 is written, the framer declares oof when 2 f-bit errors out of 4 consecutive f-bits are observed. (these two ratios are recommended in tr-tsy-000009 section 4.1.2) when the frmr is configured for g.747 operation (the g747 bit is set to logic 1), the oof status is declared when 4 consecutive framing word errors occur (as per ccitt rec. g747 section 4), regardless of the m2o5 bit setting.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 116 word: the word bit determines the method of accumulating g.747 framing errors. if the word bit is a logic 0, each frame alignment signal (fas) bit error results in a single ferr count. if the word bit is a logic 1, one or more bit errors in a fas word result in a single ferr count. g747: the g747 bit configures the frmr for g.747 operation. if the g747 bit is a logic 1, the frmr will process a g.747 signal. if the g747 bit is a logic 0, the frmr will process a ds2 signal as defined in ansi t1.107 section 7.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 117 registers 41h, 51h, 61h, 71h, 81h, 91h and a1h: ds2 frmr interrupt enable bit type function default bit7 r/w cofae 0 bit6 unused x bit5 r/w rede 0 bit4 r/w ferfe 0 bit3 r/w rese 0 bit2 r/w aise 0 bit1 r/w oofe 0 bit0 unused x oofe, aise, ferfe, rede: the oofe, aise, ferfe and rede bits are interrupt enables. a change of state on a corresponding ds2 frmr status causes the interrupt output, intb, to be asserted low when the corresponding interrupt enable bit is written with a logic 1. cofae: the cofae bit is an interrupt enable. a change of frame alignment (cofa) event causes the interrupt output to be set high when the cofae bit is written with a logic 1. rese: the rese bit is an interrupt enable. a change in the debounced value of the reserved bit in set ii when in g.747 mode causes the interrupt output to be set high when the rese bit is written with a logic 1. the debounced value of the reserved bit only changes when the reserved bit is the same for two consecutive frames. the rese bit has no effect in ds2 mode. the interrupt output, intb, is deasserted when the interrupt status register is read if its assertion was a result an oof, ais, ferf, red, res, or cofa event.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 118 registers 42h, 52h, 62h, 72h, 82h, 92h and a2h: ds2 frmr interrupt status bit type function default bit7 r cofai x bit6 unused x bit5 r redi x bit4 r ferfi x bit3 r resi x bit2 r aisi x bit1 r oofi x bit0 unused x oofi, aisi, ferfi, redi: the oofi, aisi, ferfi and redi bits are interrupt status indicators. a change of state on the corresponding ds2 frmr status causes the corresponding interrupt status bit to be set to logic 1. resi: the resi bit is an interrupt status indicator. a change in the debounced value of the reserved bit in set ii when in g.747 mode causes this bit to be set to logic 1. the debounced value of the reserved bit only changes when the reserved bit is the same for two consecutive frames. this bit has no effect in ds2 mode. cofai: the cofai bit is an interrupt status indicator. as per tr-tsy-000820, the change of frame alignment (cofa) interrupt is only asserted if a frame search results in a frame alignment which is different from the prior frame alignment. the interrupt status bits are cleared when the ds2 frmr interrupt status register is read.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 119 registers 43h, 53h, 63h, 73h, 83h, 93h and a3h: ds2 frmr status bit type function default bit7 unused x bit6 unused x bit5 r redv x bit4 r ferfv x bit3 r resv x bit2 r aisv x bit1 r oofv x bit0 unused x oofv, aisv, ferfv, redv: the oofv, aisv, ferfv and redv bits in this register reflect the status of the corresponding ds2 frmr value. the oofv bit is a logic 1 if the ds2 framer is presently out-of-frame. the aisv bit is a logic 1 if ais has been declared. in ds2 mode, the ferfv bit reflects the debounced state of the x bit (first bit of the m4-subframe). if the x-bit has been a zero for two consecutive m- frames, the ferfv bit becomes a logic 1. if the x-bit has been a one for two consecutive m-frames, the ferfv bit becomes a logic 0. in g.747 mode, ferfv bit reflects the debounced state of the remote alarm indication (rai, bit 1 of set ii) bit. if the rai bit has been a one for two consecutive frames, the ferfv bit becomes a logic 1. if the rai bit has been a zero for two consecutive frames, the ferfv bit becomes a logic 0. a six frame latency of the ferfv status ensures a virtually 100% probability of freezing correctly in ds2 mode upon an out-of-frame condition and a better than 99.9% probability of freezing correctly in g.747 mode. redv: the redv bit is a logic 1 if an out-of-frame condition has persisted for 9.9 ms (6.9ms in g.747 mode). this is less than 1.5 times the maximum average reframe time allowed. the redv status will remain asserted for 9.9 ms (6.9ms in g.747 mode) after frame alignment has been declare and then become logic 0.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 120 resv: the resv bit reflects the debounced state of the reserved bit in set ii when in g.747 mode. the debounced value of the reserved bit only changes when the reserved bit is the same for two consecutive frames.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 121 registers 44h, 54h, 64h, 74h, 84h, 94h and a4h: ds2 frmr monitor interrupt enable/status bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 r/w inte 0 bit 1 r intr 0 bit 0 r ovr 0 inte: the interrupt enable (inte) bit allows the ds2 frmr to assert the intb output upon register transfers. a logic 1 in the inte bit position enables the ds2 frmr to generate a microprocessor interrupt when the counter values are transferred to the holding registers. a logic 0 in the inte bit position disables the ds2 frmr from generating an interrupt. when the tsb is reset, the inte bit is set to logic 0, disabling the interrupt. the interrupt is cleared when this register is read if its assertion was a result a transfer operation. intr: the interrupt (intr) bit indicates the current status of the internal interrupt signal. a logic 1 in this bit position indicates that a transfer of counter values to the holding registers has occurred; a logic 0 indicates that no transfer has occurred. this bit is set to logic 0 when this register is read. the value of the intr bit is not affected by the value of the inte bit. ovr: the overrun (ovr) bit indicates the overrun status of the holding registers. a logic 1 in this bit position indicates that a previous interrupt has not been cleared before the end of the next accumulation interval, and that the contents of the holding registers have been overwritten. a logic 0 indicates that no overrun has occurred. this bit is reset to logic 0 when this register is read.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 122 to generate a transfer of the counters to the holding registers, a microprocessor write to the global pmon update register is required.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 123 registers 45h, 55h, 65h, 75h, 85h, 95h and a5h: ds2 frmr ferr count bit type function default bit 7 r ferr[7] x bit 6 r ferr[6] x bit 5 r ferr[5] x bit 4 r ferr[4] x bit 3 r ferr[3] x bit 2 r ferr[2] x bit 1 r ferr[1] x bit 0 r ferr[0] x this register indicates the number of ds2 framing bit error events or g.747 framing word errors that occurred during the previous accumulation interval. a ds2 framing bit error event is either an m-bit or and f-bit error. one or more bit errors in a g.747 frame alignment signal results in a single framing word error. a transfer operation can be triggered by writing to the global pmon update register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 124 registers 46h, 56h, 66h, 76h, 86h, 96h and a6h: ds2 frmr perr count (lsb) bit type function default bit 7 r perr[7] x bit 6 r perr[6] x bit 5 r perr[5] x bit 4 r perr[4] x bit 3 r perr[3] x bit 2 r perr[2] x bit 1 r perr[1] x bit 0 r perr[0] x registers 47h, 57h, 67h, 77h, 87h, 97h and a7h: ds2 frmr perr count (msb) bit type function default bit 7 r unused x bit 6 r unused x bit 5 r unused x bit 4 r perr[12] x bit 3 r perr[11] x bit 2 r perr[10] x bit 1 r perr[9] x bit 0 r perr[8] x these registers indicate the number of g.747 parity error events that occurred during the previous accumulation interval. a transfer operation can be triggered by writing to the global pmon update register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 125 registers 48h, 58h, 68h, 78h, 88h, 98h and a8h: mx12 configuration and control bit type function default bit7 r/w g747 0 bit6 r/w pinv 0 bit5 r/w minv 0 bit4 r/w finv 0 bit3 r/w xais 0 bit2 r/w xferf 0 bit1 r/w xres 0 bit0 r/w inte 0 inte: when set high, the inte bit enables the activation of the interrupt output, intb, whenever any of the lbri[4:1] bits are set high in the loopback request interrupt register. interrupts are masked when inte is cleared low. xres: the xres bit only has effect in g.747 mode. when xres is set high and ais is not being transmitted, the reserved bit (set ii, bit 3) is set to 0; otherwise, the transmitted reserved bit is set to 1. xferf: when set high, the xferf bit enables the transmission of the far end receive failure (ferf) signal in the ds2 output stream when in ds2 mode (i.e. g747 bit low). when xferf is set high, the transmitted x bit is set to 0, provided that ais is not being transmitted; otherwise the transmitted x bit is set to 1. when in g.747 mode (i.e. g747 bit high), the remote alarm indication (rai) is set to 1 when xferf is set high; otherwise, the transmitted rai bit is set to 0 unless ais is being transmitted. xais: when set high, the xais bit enables the transmission of the alarm indication signal (ais) in the 6312 kbit/s output stream. when xais is set high, the transmitted data is set to all ones; otherwise the transmitted data is not affected.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 126 finv: when finv is set high and g747 is low, all the transmitted f bits in the ds2 output stream are logically inverted for diagnostic purposes. if g747 is low when finv is set high, the nine bit frame alignment signal (111010000) is logically inverted (i.e. 000101111). minv: when minv is set high, the transmitted m bits in the ds2 output stream are inverted for diagnostic purposes. this only has effect when the g747 bit is low. pinv: when pinv is set high, the transmitted parity bit in the g.747 formatted output stream is inverted for diagnostic purposes. this only has effect when the g747 bit is high. g747: when g747 is high, the mx12 supports ccitt recommendation g.747. in this mode, three 2048 kbit/s tributaries are multiplexed into and demultiplex out of a 840 bit frame. if g747 is low, the frame format is compatible with ds2 as specified in the ansi t1.107 standard.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 127 registers 49h, 59h, 69h, 79h, 89h, 99h and a9h: mx12 loopback code select register bit type function default bit7 unused x bit6 unused x bit5 unused x bit4 unused x bit3 unused x bit2 unused x bit1 r/w lbcode[1] 0 bit0 r/w lbcode[0] 0 lbcode[1:0]: the lbcode[1:0] bits select the valid state for a loopback request coded in the c-bits of the ds2 signals. transmit and receive are not independent; the same code is expected in the demultiplexed ds2 as is inserted in the ds2 to be multiplexed. the following table gives the correspondence between lbcode[1:0] bits and the valid codes: lbcode[1:0] loopback code 00 c1 = c2 and c1 = c3 01 c1 = c3 and c1 = c2 10 c2 = c3 and c1 = c2 11 c1 = c2 and c1 = c3 if lbcode[1:0] is 'b00 or 'b11, the loopback code is as per ansi t1.107 section 7.2.1.1 and tr-tsy-000009 section 3.7. because tr-tsy-000233 section 5.3.14.1 recommends compatibility with non-compliant existing equipment, the two other loopback command possibilities are also supported. the lbcode[1:0] bits will also select the valid state for a loopback request coded in the c-bits of the g.747 formatted signal. again, the transmit and
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 128 receive are not independent; the same code is expected in the demultiplexed g.747 stream as is inserted in the g.747 stream to be multiplexed. the valid codes are the same as those for the ds2 formatted stream given in the table above. the lbcode[1:0] bits become logical 0 upon either a hardware or software reset.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 129 registers 4ah, 5ah, 6ah, 7ah, 8ah, 9ah and aah: mx12 ais insert register bit type function default bit7 r/w mais[4] 0 bit6 r/w mais[3] 0 bit5 r/w mais[2] 0 bit4 r/w mais[1] 0 bit3 r/w dais[4] 0 bit2 r/w dais[3] 0 bit1 r/w dais[2] 0 bit0 r/w dais[1] 0 dais[4:1]: setting any of the dais[4:1] bits activates insertion of the alarm indication signal (all ones) into the corresponding low speed stream demultiplexed from the 6312 kbit/s high speed input signal. demux ais insertion takes place after the point where remote loopback may be invoked using the loopback activate register thus allowing demux ais to be inserted into the through path while a loopback is activated, if desired. mais[4:1]: setting any of the mais[4:1] bits activates insertion of the alarm indication signal (all ones) into the corresponding low speed stream multiplexed into the 6312 kbit/s high speed output signal. mux ais insertion takes place before the point where remote loopback may be invoked using the loopback activate register and thus mux ais cannot be inserted while a loopback is activated.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 130 registers 4bh, 5bh, 6bh, 7bh, 8bh, 9bh and abh: mx12 loopback activate register bit type function default bit7 r/w ilbr[4] 0 bit6 r/w ilbr[3] 0 bit5 r/w ilbr[2] 0 bit4 r/w ilbr[1] 0 bit3 r/w lba[4] 0 bit2 r/w lba[3] 0 bit1 r/w lba[2] 0 bit0 r/w lba[1] 0 lba[4:1]: setting any of the lba[4:1] bits activates loopback of the corresponding low speed stream from the high speed input signal to the high speed output signal. lba[4] has no effect in g.747 mode, but lba[3:1] activates the loopback of the corresponding 2048 kbit/s signal. the demultiplexed ds1 signals continue to present valid payloads while loopbacks are activated. the mx12 ais insert register allows insertion of ds1 ais if required. ilbr[4:1] in ds2 mode, setting any of the ilbr[4:1] bits enables the insertion of a loopback request in the corresponding ds1 stream in the ds2 output signal. the format of the loopback request is determined by the lbcode[1:0] bits in the loopback code select mx12 register. in g.747 mode, ilbr[j] inverts bit c j1 , c j2 or c j3 in the g.747 frame in an analogous fashion.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 131 registers 4ch, 5ch, 6ch, 7ch, 8ch, 9ch and ach: mx12 loopback interrupt register bit type function default bit7 r lbri[4] x bit6 r lbri[3] x bit5 r lbri[2] x bit4 r lbri[1] x bit3 r lbrd[4] x bit2 r lbrd[3] x bit1 r lbrd[2] x bit0 r lbrd[1] x lbrd[4:1]: the lbrd[4:1] bits are set high while a loopback request is detected for the corresponding low speed stream in the high speed input signal. the lbrd[4:1] bits are set low otherwise. the format of the loopback request expected is determined by the lbcode[1:0] bits in the mx12 loopback code select register. as per tr- tsy-000009 section 3.7, the loopback request must be present for five successive m-frames before declaration of detection. removal of the loopback request is declared when it has been absent for five successive m- frames. lbri[4:1]: the lbri[4:1] bits are set high when a loopback request is asserted or deasserted for the corresponding low speed stream in the high speed input signal. the lbri[4:1] bits are set high whenever the corresponding lbrd[4:1] bits change state. if interrupts are enabled using the inte bit in the configuration register then the interrupt output, intb, is activated. the lbri[4:1] bits are cleared low immediately following a read of the register, acknowledging the interrupt and deactivating the intb output.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 132 11 test features description the d3mx contains test features for both production testing and board testing. simultaneously asserting the csb, rdb and wrb inputs causes all output pins and the data bus to be held in a high-impedance state. this test feature may be used for board testing. test mode registers are used to apply test vectors during production testing of the d3mx. test mode registers (as opposed to normal mode registers) are selected when trs (a[8]) is high. test mode registers may also be used for board testing. when all of the constituent telecom system blocks within the d3mx are placed in test mode 0, device inputs may be read and device outputs may be forced via the microprocessor interface (refer to the section "test mode 0" for details). 11.1 test mode register memory map address register 100h-10ch reserved 10ch tran test register 0 10dh tran test register 1 10eh tran test register 2 10fh reserved 110h pmon test register 0 111h pmon test register 1 112h pmon test register 2 113h - 11fh reserved 120h xfdl test register 0 121h xfdl test register 1 122h - 123h reserved 124h rfdl test register 0 125h rfdl test register 1 126h-127h reserved
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 133 address register 128h mx23 test register 0 129h mx23 test register 1 12ah mx23 test register 2 12bh mx23 test register 3 12ch - 12fh reserved 130h xboc test register 0 131h xboc test register 1 132h rboc test register 0 133h rboc test register 1 134h ds3 frmr test register 0 135h ds3 frmr test register 1 136h ds3 frmr test register 2 137h ds3 frmr test register 3 138h - 13fh reserved 140h ds2 #1 frmr test register 0 141h ds2 #1 frmr test register 1 142h ds2 #1 frmr test register 2 143h - 147h reserved 148h ds2 #1 mx12 test register 0 149h ds2 #1 mx12 test register 1 14ah ds2 #1 mx12 test register 2 14bh - 14fh reserved 150h ds2 #2 frmr test register 0 151h ds2 #2 frmr test register 1 152h ds2 #2 frmr test register 2 153h - 157h reserved 158h ds2 #2 mx12 test register 0 159h ds2 #2 mx12 test register 1
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 134 address register 15ah ds2 #2 mx12 test register 2 15bh - 15fh reserved 160h ds2 #3 frmr test register 0 161h ds2 #3 frmr test register 1 162h ds2 #3 frmr test register 2 163h - 167h reserved 168h ds2 #3 mx12 test register 0 169h ds2 #3 mx12 test register 1 16ah ds2 #3 mx12 test register 2 16bh - 16fh reserved 170h ds2 #4 frmr test register 0 171h ds2 #4 frmr test register 1 172h ds2 #4 frmr test register 2 173h - 177h reserved 178h ds2 #4 mx12 test register 0 179h ds2 #4 mx12 test register 1 17ah ds2 #4 mx12 test register 2 17bh - 17fh reserved 180h ds2 #5 frmr test register 0 181h ds2 #5 frmr test register 1 182h ds2 #5 frmr test register 2 183h - 187h reserved 188h ds2 #5 mx12 test register 0 189h ds2 #5 mx12 test register 1 18ah ds2 #5 mx12 test register 2 18bh - 18fh reserved 190h ds2 #6 frmr test register 0 191h ds2 #6 frmr test register 1
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 135 address register 192h ds2 #6 frmr test register 2 193h - 197h reserved 198h ds2 #6 mx12 test register 0 199h ds2 #6 mx12 test register 1 19ah ds2 #6 mx12 test register 2 19bh - 19fh reserved 1a0h ds2 #7 frmr test register 0 1a1h ds2 #7 frmr test register 1 1a2h ds2 #7 frmr test register 2 1a3h - 1a7h reserved 1a8h ds2 #7 mx12 test register 0 1a9h ds2 #7 mx12 test register 1 1aah ds2 #7 mx12 test register 2 1abh - 1ffh reserved 00-ffh normal mode registers 07h master test register notes on register bits: 1. writing values into unused register bits has no effect. reading back unused bits can produce either a logic one or a logic zero; hence unused bits should be masked off by software when read. 2. writeable register bits are not initialized upon reset unless otherwise noted.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 136 address 07h: master test bit type function default bit 7 r/w vclk_iotst x bit 6 unused x bit 5 unused x bit 4 w pmctst x bit 3 w dbctrl x bit 2 r/w iotst x bit 1 w hizdata x bit 0 r/w hizio x the master test register is provided at d3mx read/write address 07h. this register is used to select d3mx test features. all bits, except for pmctst, are reset to zero by a hardware reset of the d3mx; a software reset of the d3mx does not affect the state of the bits in this register. vclk_iotst: the vclk_iotst bit replaces the rclk/vclk input as the test clock when the iotst bit is a logic 1. some sense points require a rising edge on the test clock to clock in the value on the pin. this bit satisfies the requirement without needing the rclk/vclk input to toggle. pmctst: the pmctst bit is used to configure the d3mx for pmc's manufacturing tests. when pmctst is set to logic 1, the d3mx microprocessor port becomes the test access port used to run the pmc "canned" manufacturing test vectors. the pmctst bit is logically "ored" with the iotst bit, and can only be cleared by setting csb to logic 1. dbctrl: the dbctrl bit is used to pass control of the data bus drivers to the csb pin. when the dbctrl bit is set to logic 1, the csb pin controls the output enable for the data bus. while the dbctrl bit is set, holding the csb pin high causes the d3mx to drive the data bus and holding the csb pin low tri- states the data bus. the dbctrl bit overrides the hizdata bit. the
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 137 dbctrl bit is used to measure the drive capability of the data bus driver pads. iotst: the iotst bit is used to allow normal microprocessor access to the test registers and control the test mode in each tsb block in the d3mx for board level testing. when iotst is a logic 1, all blocks are held in test mode and the microprocessor may write to a block's test mode 0 registers to manipulate the outputs of the block and consequently the device outputs (refer to the "test mode 0 details" in the "test features" section). hizio, hizdata: the hizio and hizdata bits control the tri-state modes of the d3mx . while the hizio bit is a logic 1, all output pins of the d3mx except the data bus are held in a high-impedance state. the microprocessor interface is still active. while the hizdata bit is a logic 1, the data bus is also held in a high- impedance state which inhibits microprocessor read cycles. 11.2 test mode 0 in test mode 0, the d3mx allows the logic levels on the device inputs to be read through the microprocessor interface, and allows the device outputs to be forced to either logic level through the microprocessor interface. to enable test mode 0, the iotst bit in the test mode select register is set to logic 1 and the following addresses must be written with 00h: 10dh, 111h, 121h, 125h, 129h, 131h, 133h, 135h, 141h, 149h, 151h, 159h, 161h, 169h, 171h, 179h, 181h, 189h, 191h, 199h, 1a1h and 1a9h. reading the following address locations returns the values for the indicated inputs :
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 138 table 1 - test mode address locations C read from inputs addr bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 10eh tdlsig/ tdludr 3 toh tohen 120h tdleomi 128h timfp 4 ticlk 134h rneg/ rlcv 1,4 rpos/ rdat 1,4 rclk 2 14ah td1dat4 td1dat3 td1dat2 td1dat1 td1clk4 td1clk3 td1clk2 td1clk1 15ah td1dat8 td1dat7 td1dat6 td1dat5 td1clk8 td1clk7 td1clk6 td1clk5 16ah td1dat12 td1dat11 td1dat10 td1dat9 td1clk12 td1clk11 td1clk10 td1clk9 17ah td1dat16 td1dat15 td1dat14 td1dat13 td1clk16 td1clk15 td1clk14 td1clk13 18ah td1dat20 td1dat19 td1dat18 td1dat17 td1clk20 td1clk19 td1clk18 td1clk17 19ah td1dat24 td1dat23 td1dat22 td1dat21 td1clk24 td1clk23 td1clk22 td1clk21 1aah td1dat28 td1dat27 td1dat26 td1dat25 td1clk28 td1clk27 td1clk26 td1clk25 notes: 1. if the rinv and the ds3 frmr uni register bits are logic one, the values read are active low. 2. if the rfall register bit is a logic 1, the value read is inverted. 3. the texhdlc register bit must be a logic 1 to sense this input. 4. these inputs must be clocked by the vclk_iotst bit before being read. this requires writing a logic 0 then a logic 1 to the vclk_iotst bit . writing the following address locations forces the outputs to the value in the corresponding bit position: table 2 - test mode address locations C write to outputs addr bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 10ch tneg/ tmfp 1,3 tpos/ tdat 2,3 tneg/ tmfp 2,3 tpos tdat 1,3 / tclk 4 10eh tdlclk/ tdlint 5 tohfp tohclk 110h intb 7
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 139 addr bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 120h tdlsig/ tdludr 6 tdlclk/ tdlint 6 124h rdlsig/ rdleom 9 rdlclk/ rdlint 9 128h gd2clk intb 7 134h intb 7 rlos rohp rmsfp rmfp rodat roclk 136h rohdat rohclk 137h roof rexz rohfp rdlclk/ rdlint 8 rdlsig/ rdleom 8 140h intb 7 148h intb 7 14ah rd1dat4 rd1dat3 rd1dat2 rd1dat1 rd1clk4 rd1clk3 rd1clk2 rd1clk1 150h intb 7 158h intb 7 15ah rd1dat8 rd1dat7 rd1dat6 rd1dat5 rd1clk8 rd1clk7 rd1clk6 rd1clk5 160h intb 7 168h intb 7 16ah rd1dat12 rd1dat11 rd1dat10 rd1dat9 rd1clk12 rd1clk11 rd1clk10 rd1clk9 170h intb 7 178h intb 7 17ah rd1dat16 rd1dat15 rd1dat14 rd1dat13 rd1clk16 rd1clk15 rd1clk14 rd1clk13 180h intb 7 188h intb 7 18ah rd1dat20 rd1dat19 rd1dat18 rd1dat17 rd1clk20 rd1clk19 rd1clk18 rd1clk17 190h intb 7 198h intb 7 19ah rd1dat24 rd1dat23 rd1dat22 rd1dat21 rd1clk24 rd1clk23 rd1clk22 rd1clk21 1a0h intb 7 1a8h intb 7 1aah rd1dat28 rd1dat27 rd1dat26 rd1dat25 rd1clk28 rd1clk27 rd1clk26 rd1clk25 notes: 1. this bit only has effect if the tuni register bit is logic one.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 140 2. this bit only has effect if the tuni register bit is logic zero. 3. these bits are only presented on the output after being clocked by the tclk output. this requires writing a logic 0 then a logic 1 to the tclk bit . 4. the tclk output is inverted if the trise bit is a logic 0. 5. this bit only has effect if the texhdlc register bit is logic 1. 6. this bit only has effect if the texhdlc register bit is logic 0. the polarity of the signal forced on the output pin is determined by the state of the tintpol and tudrpol register bits. 7. writing a logic 1 to any intb bit asserts the intb output low. 8. this bit only has effect if the rexhdlc register bit is logic 1. 9. this bit only has effect if the rexhdlc register bit is logic 0. the polarity of the signal forced on the output pin is determined by the state of the rintpol and reompol register bits. the state of the configuration registers must be considered. to make board testing more straight forward, it is recommended that the normal mode registers be initialized to the following state: write register 02h with 00h (clears byp[7:1]) write register 03h with c0h (sets rexhdlc and texhdlc) or with 0fh (sets reompol,tudrpol,rintpol, tintpol). write register 04h with 00h (clears lineais[1:0], llbe and dlbe.) write register 05h with 08h (sets trise. clears tinv, tuni, rinv, rfall.) write register 07h with 04h (sets iotst to put device into test mode.) write register 34h with 00h (clears ds3 frmr uni bit.) if the registers are in a different state than this, adjustments must be made for inversion of assertion levels.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 141 12 operation 12.1 using the internal data link transmitter upon reset of the d3mx, the xfdl should be disabled by setting the en bit in the configuration/control register to logic 0. if data is not ready to be transmitted, the tdlint output should also be masked by setting the inte bit to logic 0. when a frame (or frames) of data are ready to be transmitted, the configuration/ control register should be initialized for transmission: if the fcs is desired, the crc bit should be set to logic 1; if the block is to be used in interrupt driven mode, interrupts should be enabled by setting the inte bit to logic 1. finally, the xfdl can be enabled by setting the en bit to logic 1. the xfdl can be used in a polled, interrupt driven, or dma-controlled mode for the transfer of frame data. in the polled mode, the tdlint and tdludr outputs of the xfdl are not used, and the processor controlling the xfdl must periodically read the status register to determine when to write to the transmit data register. in the interrupt driven mode, the processor controlling the xfdl uses the tdlint output to determine when to write to the transmit data register. in the dma controlled mode, the tdlint output of the xfdl is used as a dma request input to the dma controller, and the tdludr output is used as an interrupt to the processor to allow handling of exceptions. if the xfdl data transfer is operating in the polled mode, then a timer periodically starts up a service routine, which should process data as follows: 1. read the xfdl status register and check the udr and intr bits. 2. if udr=1, then clear the status register, set the udr bit in the xfdl configuration register to logic 0, and restart the current frame. 3. if intr=1, then: a) if there is still data to send, then write the next data byte to the transmit data register; b) f all bytes in the frame have been sent, then set the eom bit in the xfdl configuration register to logic 1, and set the inte bit to logic 0. alternatively, assert the tdleomi input. 4. read the status register and check the udr bit.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 142 5. if udr=1, then clear the status register, clear the udr bit (deassert the tdleomi input and clear eom, if set) in the xfdl configuration register to logic 0. restart the current frame. in the case of interrupt driven data transfer, the tdlint output of the xfdl is connected to the interrupt input of the processor, and the interrupt service routine should process the data exactly as described above for the polled mode. the xfdl can also be used with a dma controller to process the frame data. in this case, the tdludr output is connected to the processor interrupt input. the tdlint output of the xfdl is connected to the dma request input of the dma controller. the dma "end" signal from the controller can be connected to the tdleomi input. the dma controller writes a data byte to the xfdl whenever the tdlint output is asserted. upon writing the last byte of the packet to xfdl, the dma asserts the tdleomi input. note that the tdleomi input is expected to be "glitch-free" and, when pulsed high, sets the eom register bit in the transmitter configuration register. the eom register bit is used by the transmitter to determine the course of action when the current data byte is exhausted. if there is a problem during transmission and an underrun condition occurs, then the tdludr output goes high and the processor is interrupted. the processor can then halt the dma controller, clear the problem condition, reset the frame data pointers, and restart the dma controller to resend the data frame. 12.2 using the internal data link receiver on power up of the d3mx, the rfdl should be disabled by setting the en bit in the configuration register to logic 0. the interrupt control/status register should then be initialized to select the fifo buffer fill level at which an interrupt will be generated. after the interrupt control/status register has been written to, the rfdl can be enabled at any time by setting the en bit in the configuration register to logic 1. when the rfdl is enabled, it will assume that the link status is idle (all ones) and immediately begin searching for flags. when the first flag is found, an interrupt will be generated (if enabled), and the byte received before the first flag was detected will be written into the fifo buffer. because the flg and eomr bits are passed through the buffer, this dummy write allows the status register to accurately reflect the current state of the data link. a status register read after a data register read of the dummy byte will return eomr as logic 1 and flg as logic 1. the first interrupt and data byte read after the rfdl is enabled (or tr bit set to logic 1) is an indication of the link status, and the data byte should therefore be discarded. it is up to the controlling processor to keep track of the
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 143 link state as idle (all ones or bit-oriented messages active) or active (flags received). the rfdl can be used in a polled, interrupt driven, or dma controlled mode for the transfer of frame data. in the polled mode, the rdlint and rdleom outputs of the rfdl are not used, and the processor controlling the rfdl must periodically read the status register to determine when to read the data register. in the interrupt driven mode, the processor controlling the rfdl uses the rdlint output to determine when to read the data register. in the dma controlled mode, the rdlint output of the rfdl is used as a dma request input to the dma controller, and the rdleom output is used as an interrupt to the processor to allow handling of exceptions and as an indication of when to process a frame. in the case of interrupt driven data transfer from the rfdl to the processor, the rdlint output of the rfdl is connected to the interrupt input of the processor. the processor interrupt service routine should process the data in the following order: 1. read the rfdl data register. 2. read the rfdl status register to check for, in order, underrun, ovr, flg, eomr, and fe. 3. if the fifo has underrun (i.e. the status register returns 00 hex), then discard the last data byte and wait for the next interrupt. 4. if ovr=1, then discard the last frame and wait for the next interrupt. 5. if flg=0 (i.e. an abort has been received) and the link state was active, then set the link state to inactive, discard the last frame, and wait for the next interrupt. 6. if flg=1 and the link state was inactive, then set the link state to active, discard the last data byte, and wait for the next interrupt. 7. otherwise, save the last data byte read. 8. if eomr=1, then check the crc, nvb and process the frame. 9. if fe=0, then go to step 1, else wait for the next interrupt. the interrupt service routine can optionally read the status register first to check for an overrun condition, and then for available data, before advancing to step one above.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 144 the link state is typically a local software variable. the link state is inactive if the rfdl is receiving all ones or receiving bit-oriented codes which contain a sequence of eight ones. the link state is active if the rfdl is receiving flags or data. if the rfdl data transfer is operating in the polled mode, then processor operation is exactly as shown above for the interrupt driven mode, except that the entry to the service routine is from a timer, rather than an interrupt. in the polled mode, the option of reading the status register first should be used to avoid unnecessary reads of the data register. the rfdl can also be used with a dma controller to process the frame data. in this case, the rdleom output is connected to the processor interrupt input. the rdlint output of the rfdl is connected through a gate to the dma request input of the dma controller. the gate optionally inhibits the dma request if the rdleom output is high. the dma controller reads the data bytes from the rfdl whenever the rdlint output is asserted. when the current byte read from the data register is the last byte in a frame (due to an end-of-message or an abort), or an overrun condition occurs, then the rdleom output goes high. the dma controller is inhibited from reading any more bytes, and the processor is interrupted. the processor can then halt the dma controller, read the status register, process the frame, and finally reset the dma controller to process the data for the next frame.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 145 figure 6 - typical data frame transmit 87654321 01111110 flag address (high) (low) control frame check sequence (fcs) 01111110 flag bit: data bytes received and transferred to the fifo, bit 1 first data bytes written to the transmit data register and serially transmitted, bit 1 first appended after eom is set, if crc is set receive bit 1 is the first serial bit to be transmitted or received. both the address and control bytes must be supplied by an external processor and are shown for reference purposes only. 12.2.1 key used on subsequent diagrams: flag - flag sequence (01111110) abort - abort sequence (01111111) d1 - dn - n frame data bytes r - remainder bits (less than 8) c1, c2 - crc-ccitt information b1, b2, b3 - groupings of 8 bits
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 146 figure 7 - rfdl normal data and abort sequence serial data extracted from datalink rdlint rdleom d[7:0] flag d1 d2 d3 dn rc1 c2 flag d1 b1 b2 b3 d1 dn-2 dn-1 dn b1 b2 b3 d2 dn-1 dn-3 d1 b1 abort eom eom b1 r abort this diagram shows the relationship between rfdl inputs and outputs for the case where interrupts are programmed to occur when one byte is present in the fifo buffer. the rfdl is assumed to be operating in the interrupt driven mode. each read shown is composed of two register reads: first a read of the data register, followed by a read of the status register. a read of the data register deasserts the rdlint output if no more data exists in the fifo buffer. the status of the fe bit returned in the status register read will indicate the fifo buffer fill status as well. the data register read dn-2 is shown to occur after two bytes have been written into the buffer. the rdlint output is not deasserted after the first data register read because a data byte still remains to be read. the rdlint output is deasserted after data register read dn-1. the fe bit will be logic 0 in status register read dn-2 and logic 1 in status register read dn-1. the rdleom output goes high as soon as the last byte in the frame is read from the data register. the rdlint output will be deasserted if the fifo buffer is empty. the next status register read will return a value of logic 1 for the eomr and flg bits, and cause the rdleom output of the rfdl to return low. in the next frame, the first data byte is received, and after a delay of ten bit periods, it is written to the fifo buffer, and read by the processor after the interrupt. when the abort sequence is detected, the data received up to the abort is written to the fifo buffer and an interrupt generated. the processor then reads the partial byte from the data register and the rdleom output is set high. the processor then reads the status register which will return a value of logic 1 for the eomr and flg bits, and set the rdleom output low. the fifo buffer is not cleared when an abort is detected. all bytes received up to the abort are available to be read.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 147 after an abort, the rfdl state machine will be in the receiving all ones state, and the data link status will be idle. when the first flag is detected, a new interrupt will be generated, with a dummy data byte loaded into the fifo buffer, to indicate that the data link is now active. figure 8 - rfdl fifo overrun serial data extracted from datalink rdlint rdleom d[7:0] flag d1 d2 d3 dn r c1 c2 flag d1 b1 b2 b3 d1 statusrd d2 dn-1 ovr r abort this diagram shows the relationship between rfdl inputs and outputs for the case where interrupts are programmed to occur when two data bytes are present in the fifo buffer. each read is composed of two register reads, as described above. in this example, data is not read by the end of b2. an overrun occurs since unread data (dn-3) has been overwritten by b1. this sets the rdleom output high, and resets both the rfdl and the fifo buffer. the rfdl is held disabled until the status register is read. the start flag sequence is not detected since the rfdl is still held disabled when it occurs. consequently, the rfdl will ignore the entire frame including the abort sequence (since it has not occurred in a valid frame or during flag reception, according to the rfdl).
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 148 figure 9 - xfdl normal data sequence flag d1 d2 dn crc1 crc2 flag d1 d1 d2 d3 d4 d2 d3 tdlint d[7:0] inte eom d1 inte inte serial data inserted into datalink this diagram shows the relationship between xfdl inputs and outputs for the case where interrupts and crc are enabled for regular data transmission. the process is started by setting the inte bit in the configuration/control register to logic 1, thus enabling the tdlint signal. when tdlint is asserted, the interrupt service routine is started, which writes the first byte (d1) of the data frame to the transmit data register. when this byte begins to be shifted out on the data link, tdlint is asserted. this restarts the interrupt service routine, and the next data byte (d2) is written to the transmit data register. when d2 begins to be shifted out on the data link, tdlint is asserted again. this cycle continues until the last data byte (dn) of the frame is written to the transmit data register. when dn begins to be shifted out on the data link, tdlint again is asserted. since all the data has been sent, the interrupt service routine sets the eom bit in the configuration/control register to logic 1 (or alternatively asserts the tdleomi input). the tdlint interrupt should also be disabled at this time by setting the inte bit to logic 0. the xfdl will then shift out the two-byte crc word and closing flag, which ends the frame. whenever new data is ready, the tdlint signal can be re-enabled by setting the inte bit in the configuration/control register to logic 1, and the cycle starts again.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 149 figure 10 - xfdl underrun sequence flag d1 d2 flag d2 tdlint d3 d1 d2 d3 tdludr d3 abort d1 udr d4 d1 d2 d[7:0] inte inte inte serial data inserted into datalink this diagram shows the relationship between xfdl inputs and outputs in the case of an underrun error. an underrun error occurs if the xfdl finishes transmitting the current message byte before the processor writes the next byte into the transmit data register; that is, the processor fails to write data to the xfdl in time. in this example, data is not written to the xfdl within five rising clock edges after tdlint is asserted at the beginning of the transmission of byte d3. the tdludr interrupt becomes active at this point, and an abort, followed by a flag, is sent out on the data link. meanwhile, the processor must clear the tdludr interrupt by setting the udr bit in the status register to logic 0. the tdlint interrupt should also be disabled at this time by setting the inte bit in the configuration/control register to logic 0. the data frame can then be restarted as usual, by setting the inte bit logic to 1. transmission of the frame then proceeds normally.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 150 13 functional timing figure 11 - receive ds3 high speed output timing rodat rmfp rmsfp rohp x1 bit x2 bit info c bit info info or p or m bit or f bit info info info info info info roclk
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 151 figure 12 - receive ds3 low speed timing rdlsig rdlclk rohclk rmfp rmsfp rohp rais, rlos msf #1 x1 bit msf #2 x2 bit msf #3 p1 bit msf #4 p2 bit msf #5 m1 bit msf #6 m2 bit msf #7 m3 bit roof rferf rohfp roh x1 f1 f0 f0 s1 f1 f0 x2 s7 c11 c12 c13 c21 c22 f0 c23 s2 p1 f1 f0 c31 c32 f0 c33 s3 p2 f1 f0 c71 c72 f0 c73 s7 f1 f0 c41 c42 f0 c43 s4 m1 f1 f0 c51 c52 f0 c53 s5 m2 f1 f0 c61 c62 f0 c63 s6 m3
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 152 figure 13 - transmit ds3 timing tdlsig tdlclk tohclk timfp tohen tohfp toh x f1 f0 f0 f1 f1 f0 f0 f1 f1 f0 f0 f1 f1 f0 f0 f1 f1 f0 f0 f1 f1 f0 f0 f1 f1 f0 f0 f1 xp p m0 m0 m0 f1 c11 c12 c13 c21 c22 c23 c31 c32 c33 c41 c42 c43 c51 c52 c53 c61 c62 c63 c71 c72 c73
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 153 figure 14 - tdlint timing - normal data transmission wrb & (a[8:0]='h22) tdlint tdleomi write of a byte of packet. min. 216 s max. 311 s tdludr write of next byte has not occurred <110 s write of a byte of packet. min. 216 s max. 311 s min. 216 s max. 311 s in this example successive bytes of a packet are written to the xfdl. each byte must be written within 110s from the tdlint rising edge. each subsequent assertion of tdlint occurs once all 8 bits of the current data byte have been transmitted. the range in assertion times is due to the temporal spacing of the datalink bits (3 c-bits of m-subframe 5). if another byte is not written to the data register within 110s of each tdlint assertion, an underrun condition occurs. the underrun will be indicated on the tdludr output and in the udr status bit within the xfdl interrupt status register.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 154 figure 15 - tdleomi timing - with removal of tdleomi before completion of fcs transmission wrb & (a[8:0]='h22) tdlint tdleomi write last byte of packet. write of 1st byte of next packet. < 210 s assertion suppressed by tdleomi < 846 s min 216 s max 311 s 850 s last byte + fcs transmission flag transmission assertion of the tdleomi input indicates the latest byte written to the xfdl transmit data register is the last byte of the current packet. upon assertion of tdleomi, the frame check sequence (fcs), if enabled, is appended to the packet once the last byte has been transmitted, and flags ("01111110") are transmitted in subsequent bytes until another byte is written. the tdleomi input accommodates a wide range of timing: the tdleomi input may be asserted as early as coincident with the falling edge of the write strobe for the last byte written, but must be asserted within 210 s of the assertion of the tdlint output (or int bit in the xfdl status register). this ensures that the tdleomi input is recognized before the next tdlint assertion. tdleomi must be deasserted before the write of the first byte of the next packet. if tdleomi falls too late, the first byte is also assumed to be the last, and the fcs (if enabled) and flags are appended immediately after. in the example of figure 15, the tdleomi is asserted anytime up to 210s from the tdlint rising edge and is deasserted before the fcs has been completely transmitted. the tdlint signal is suppressed by the assertion of tdleomi and remains suppressed until the fcs has completed transmission. tdlint is asserted coincident with the beginning of flag transmission and remains high until the first byte of a new packet is written into the data register. while tdlint is asserted and the xfdl tsb is awaiting the first byte of a new packet, an underrun condition cannot occur. once the first byte is written, however, the
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 155 xfdl must be serviced within 210s of tdlint assertion, otherwise an underrun condition occurs (see figure 10). note that tdleomi must be glitch free. if tdleomi is not used, it must be held low, and indication of end of message can be performed through the eom bit of the xfdl configuration register. this bit may be set by a write to the configuration register any time after the write of the last data byte, but before 210 s have elapsed since the tdlint output (or int bit in the xfdl status register) was last asserted. figure 16 - tdleomi timing - with removal of tdleomi after completion of fcs transmission wrb & (a[8:0]='h22) tdlint tdleomi write last byte of packet. write of 1st byte of next packet. < 210 s assertion suppressed by tdleomi min 216 s max 311 s 850 s last byte + fcs transmission > 0 ns flag transmission in this example, the tdleomi is asserted anytime up to 210s from the tdlint rising edge and is deasserted long after the fcs has been completely transmitted. the tdlint signal is suppressed by the assertion of tdleomi and remains suppressed until tdleomi is deasserted. tdlint is asserted immediately, indicating that the xfdl is ready to receive the first byte of a new packet. again, while the xfdl is awaiting the first byte of a new packet, an underrun condition cannot occur. once the first byte is written, however, the xfdl must be serviced within 210s of each tdlint assertion, otherwise an underrun condition occurs (see figure 10).
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 156 figure 17 - input ds3 overhead serial stream toh tohclk tohfp tohen xx - don't care bit x1 xx f1 f3 c3 f2 c1 xx c3 f4 x1 the tohfp pulse indicates when the x1 overhead bit is sampled on the toh input. both toh and tohen are sampled using the rising edge of tohclk. toh bits are only inserted if tohen is asserted. at block 8 of each m-subframe either the f4 bits or the stuff opportunity bits are inserted depending on the setting of the sbow bit in the ds3-tran configuration register. the format of the transmit overhead serial stream is as follows: table 3 - transmitt overhead format block m-subframe1234567 8 1x 1 f 1 c 1 f 2 c 2 f 3 c 3 f 4 or s 1 2x 2 f 1 c 1 f 2 c 2 f 3 c 3 f 4 or s 2 3p 1 f 1 c 1 f 2 c 2 f 3 c 3 f 4 or s 3 4p 2 f 1 c 1 f 2 c 2 f 3 c 3 f 4 or s 4 5m 1 f 1 c 1 f 2 c 2 f 3 c 3 f 4 or s 5 6m 2 f 1 c 1 f 2 c 2 f 3 c 3 f 4 or s 6 7m 3 f 1 c 1 f 2 c 2 f 3 c 3 f 4 or s 7
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 157 figure 18 - output ds3 overhead serial stream roh rohclk rohfp s1 x1 f1 c1 f2 c2 f3 c3 x2 f1 c2 f3 c3 s7 x1 the rohfp pulse indicates when the x1 overhead bit is output on the roh output stream. both roh and rohfp are updated on the falling edge of rohclk. within each m-subframe the stuff opportunity bits are extracted and output in place of the f4 framing bit. the format of the receive overhead serial stream is as follows: table 4 - receive overhead format block m-subframe12345678 1x 1 f 1 c 1 f 2 c 2 f 3 c 3 s 1 2x 2 f 1 c 1 f 2 c 2 f 3 c 3 s 2 3p 1 f 1 c 1 f 2 c 2 f 3 c 3 s 3 4p 2 f 1 c 1 f 2 c 2 f 3 c 3 s 4 5m 1 f 1 c 1 f 2 c 2 f 3 c 3 s 5 6m 2 f 1 c 1 f 2 c 2 f 3 c 3 s 6 7m 3 f 1 c 1 f 2 c 2 f 3 c 3 s 7
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 158 14 absolute maximum ratings table 5 - d3mx absolute maximum ratings ambient temperature under bias -40c to +85c storage temperature -40c to +125c supply voltage -0.5v to +6.0v voltage on any pin -0.5v to v dd +0.5v static discharge voltage 500 v latch-up current 100 ma dc input current 20 ma lead temperature +300c absolute maximum junction temperature +150c
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 159 15 d.c. characteristics (t a = -40c to +85c, v dd = 5 v 10%) table 6 - d3mx d.c. characteristics symbol parameter min typ max units conditions v il input low voltage -0.5 0.8 volts guaranteed input low voltage v ih input high voltage 2.0 v dd +0.5 volts guaranteed input high voltage v ol output or bidirectional low voltage 0.4 volts v dd = min, i ol = 4 ma for data bus pins and high speed transmit outputs and 2 ma for all others, note 3 v oh output or bidirectional high voltage 2.4 volts v dd = min, i ol = 4 ma for data bus pins and high speed transmit outputs and 2 ma for all others, note 3 v t+ reset input high voltage 3.5 volts v t- reset input low voltage 1.0 volts v th reset input hysteresis voltage 1.0 volts iilpu input low current +20 +200 a vil = gnd, notes 1, 3 iihpu input high current -10 +10 a vih = vdd, notes 1, 3 iil input low current -10 +10 a vil = gnd, notes 2, 3
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 160 symbol parameter min typ max units conditions iih input high current -10 +10 a vih = vdd, notes 2, 3 cin input capacitance 5 pf excluding package, package typically 2 pf cout output capacitance 5 pf excluding package, package typically 2 pf cio bidirectional capacitance 5 pf excluding package, package typically 2 pf iddop operating current 55 75 ma vdd = 5.5 v, outputs unloaded, all clocks at nominal frequencies notes on d.c. characteristics: 1. input pin or bidirectional pin with internal pull-up resistors. 2. input pin or bidirectional pin without internal pull-up resistors 3. negative currents flow into the device (sinking), positive currents flow out of the device (sourcing).
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 161 16 microprocessor interface timing characteristics (t a = -40c to +85c, v dd = 5 v 10%) table 7 - microprocessor read access (figure 19) symbol parameter min max units ts ar address to valid read set-up time 20 ns th ar address to valid read hold time 20 ns ts alr address to latch set-up time 20 ns th alr address to latch hold time 20 ns tv l valid latch pulse width 20 ns ts lr latch to read set-up 0 ns th lr latch to read hold 20 ns tp rd valid read to valid data propagation delay 100 ns tz rd valid read deasserted to output tri- state 20 ns tp inth valid read deasserted to intb tri- state 50 ns
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 162 figure 19 - microprocessor read access timing intb tp inth (csb+rdb) valid data d[7:0] tp rd tz rd ts ar th ar valid address a[8:0] ale ts alr tv l ts lr th alr th lr notes on microprocessor read timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum output propagation delays are measured with a 100 pf load on the microprocessor data bus, (d[7:0]). 3. a valid read cycle is defined as a logical or of the csb and the rdb signals. 4. microprocessor timing applies to normal mode register accesses only.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 163 5. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock. 6. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input. 7. in non-multiplexed address/data bus architectures, ale should be held high, parameters ts alr , th alr , tv l , th lr and ts lr are not applicable. 8. parameters th ar and ts ar are not applicable if address latching is used. table 8 - microprocessor write access (figure 20) symbol parameter min max units ts aw address to valid write set-up time 25 ns ts dw data to valid write set-up time 20 ns ts alw address to latch set-up time 20 ns th alw address to latch hold time 20 ns tv l valid latch pulse width 20 ns ts lw latch to write set-up 0 ns th lw latch to write hold 20 ns th dw data to valid write hold time 20 ns th aw address to valid write hold time 20 ns tv wr valid write pulse width 40 ns
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 164 figure 20 - microprocessor write access timing th dw valid data d[7:0] tv wr ts aw th aw ts dw (csb+wrb) a[8:0] valid address ale tv l ts alw ts lw th alw th lw notes on microprocessor write timing: 1. a valid write cycle is defined as a logical or of the csb and the wrb signals. 2. microprocessor timing applies to normal mode register accesses only. 3. in non-multiplexed address/data bus architectures, ale should be held high, parameters ts alw , th alw , tv l , th lw and ts lw are not applicable. 4. parameters th aw and ts aw are not applicable if address latching is used. 5. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 6. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 165 7. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 166 17 d3mx timing characteristics (t a = -40c to +85c, v dd = 5 v 10%) table 9 - d3mx receive ds3 input (figure 21) symbol description min max units rclk frequency (nominally 44.736 mhz ) -20 +20 ppm rclk duty cycle 40 60 % ts rpos rpos/rdat set-up time 4 ns th rpos rpos/rdat hold time 6 ns ts rneg rneg/rlcv set-up time 4 ns th rneg rneg/rlcv hold time 6 ns figure 21 - receive ds3 input timing ts rpos th rpos rpos/rdat ts rneg th rneg rneg/rclv rclk
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 167 table 10 - d3mx transmit ds3 input (figure 22) symbol description min max units ticlk frequency (nominally 44.736 mhz ) -20 +20 ppm ticlk duty cycle 40 60 % ts timfp timfp set-up time 5 ns th timfp timfp hold time 5 ns figure 22 - transmit ds3 input timing ts timfp th timfp timfp ticlk
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 168 table 11 - d3mx transmit overhead input (figure 23) symbol description min max units ts toh toh set-up time 20 ns th toh toh hold time 20 ns ts tohen tohen set-up time 20 ns th tohen tohen hold time 20 ns figure 23 - transmit overhead input timing ts toh th toh toh ts tohen th tohen tohen tohclk
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 169 table 12 - d3mx transmit tributary input (figure 24) symbol description min max units td1clkn frequency (nominally 1.544 mhz, when configured for ds1 rate operation) 3 -130 +130 ppm td1clkn frequency (nominally 2.048 mhz, when configured for e1 rate operation; not applicable for n = 4, 8, 12, 16, 20, 24, 28) 3 -50 +50 ppm td1clkn frequency (nominally 6.312 mhz, when configured for ds2 rate operation; only applicable for n = 4, 8, 12, 16, 20, 24, 28) 3 -33 +33 ppm td1clk duty cycle (all configurations) 33 67 % td2clk frequency (nominally 6.312 mhz ) 3 -33 +33 ppm td2clk duty cycle 33 67 % ts td1dat td1dat set-up time 20 ns th td1dat td1dat hold time 20 ns figure 24 - transmit tributary input timing ts td1dat th td1dat td1dat td1clk
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 170 table 13 - d3mx transmit data link input (figure 25) symbol description min max units ts tdlsig tdlsig to tdlclk set-up time 20 ns th tdlsig tdlsig to tdlclk hold time 20 ns figure 25 - transmit data link input timing ts tdlsig th tdlsig tdlsig tdlclk
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 171 table 14 - d3mx transmit data link eom input (figure 26) symbol description min max units tv teomi tdleomi pulse width 3 5ns ts1 teomi tdleomi pulse to falling edge of xfdl 3 transmit data register write set-up time 0ns ts2 teomi tdleomi pulse to next falling edge of xfdl 3 transmit data register write set-up time 0ns ts3 teomi tdleomi pulse after tdlint assertion 3 210 s figure 26 - transmit data link eom input timing ts1 teomi ts2 teomi tdleomi "write of last byte" [i.e. wrb & (a[8:0]=22h)] tv teomi ts3 teomi tdlint notes on input timing: 1. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 172 2. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input. 3. td1clkn frequency, td2clk frequency, ts1 teomi , ts2 teomi , ts3 teomi and tv teomi values are guaranteed by design - not measured. table 15 - d3mx transmit ds3 output (figure 27) symbol description min max units tclk duty cycle ticlk- 5 ticlk +5 % tp tpos tclk low to tpos/tdat valid prop. delay -2 5 ns tp tneg tclk low to tneg/tmfp valid prop. delay -2 5 ns figure 27 - transmit ds3 output timing tp tpos tpos/tdat tp tneg tneg/tmfp tclk
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 173 table 16 - d3mx receive ds3 output (figure 28) symbol description min max units tp rodat roclk low to rodat valid prop. delay -3 3 ns tp rmfp roclk low to rmfp valid propagation delay -3 3 ns tp rmsfp roclk low to rmsfp valid prop. delay -3 3 ns tp rohp roclk low to rohp valid propagation delay -3 3 ns tp rlos roclk low to rlos valid propagation delay -3 3 ns
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 174 figure 28 - receive ds3 output timing tp rodat rodat tp rmfp rmfp tp rmsfp rmsfp roclk tp rohp rohp tp rlos rlos
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 175 table 17 - d3mx receive overhead output (figure 29) symbol description min max units tp roh rohclk low to roh valid propagation delay -5 20 ns tp rohfp rohclk low to rohfp valid prop. delay -5 20 ns tp rais rohclk low to rais valid propagation delay -5 20 ns tp roof rohclk low to roof valid prop. delay -5 20 ns tp rferf rohclk low to rferf valid prop. delay -5 20 ns
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 176 figure 29 - receive overhead output timing tp roh roh rohclk tp rohfp rohfp tp rais rais tp roof roof/rred tp rferf rferf table 18 - d3mx transmit overhead output (figure 30) symbol description min max units tp tohfp tohclk low to tohfp valid prop. delay -10 20 ns
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 177 figure 30 - transmit overhead output timing tp tohfp tohfp tohclk table 19 - d3mx receive tributary output (figure 31) symbol description min max units tp rd1dat rd1clk low to rd1dat valid prop. delay -10 20 ns figure 31 - receive tributary output timing tp rd1dat rd1dat rd1clk table 20 - d3mx receive data link output (figure 32) symbol description min max units tp rdlsig rdlclk low to rdlsig valid prop. delay -10 20 ns
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 178 figure 32 - receive data link output timing tp rdlsig rdlsig rdlclk notes on output timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum output propagation delays are measured with a 20 pf load on the high-speed ds3 outputs (tclk, tpos/tdat, tneg/tmfp, roclk, rodat, rmfp, rmsfp, and rohp) and a 50 pf load on the remaining outputs.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 179 18 ordering and thermal information table 21 - d3mx ordering information pa rt n o. description PM8313-RI 208 pin copper leadframe plastic quad flat pack table 22 - d3mx thermal information pa rt n o. ambient temperature theta ja theta jc PM8313-RI -40c to 85c 50 c/w 15 c/w
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 180 19 mechanical information figure 33 - 208 pin copper leadframe plastic quad flat pack (r suffix): 1 a a2 d d1 e e1 208 e 8-12 deg. pin 1 designator a1 .25 2) dimensions shown are nominal with tolerances as indicated. 3) foot length "l" is measured at notes: 1) all dimensions in millimeter. gage plane, 0.25 above seating plane. 0-7 deg detail a a c 0-10 deg. b standoff lead coplanarity c seating plane c ccc l 0.13-0.23 see detail a 8-12 deg. 0.27 0.17 28 x 28 x 3.49 mm package type: max. nom. 4.07 min. dim. 3.64 a body size: 208 pin metric plastic quad flatpack-mqfp 0.48 3.59 3.49 30.80 30.60 28.10 28.00 0.25 a1 3.39 a2 30.40 d 27.90 d1 30.80 30.60 28.10 28.00 0.75 0.60 0.50 30.40 e 27.90 e1 0.50 l e 0.10 ccc b 0.22 the 208 pin pqfp package lead length specification has been changed from 3.20mm to the industry standard length of 2.60 mm outlined above. this change applies on all devices shipped with date codes of 9514 or later.
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer 181 notes
pm8313 d3mx data sheet pmc-920702 issue 5 m13 multiplexer none of the information contained in this document constitutes an express or implied warranty by pmc-sierra, inc. as to the suf ficiency, fitness or suitability for a particular purpose of any such information or the fitness, or suitability for a particular purpose, merchanta bility, performance, compatibility with other parts or systems, of any of the products of pmc-sierra, inc., or any portion thereof, referred to in this document. pmc-sierra, inc. expressly disclaims all representations and warranties of any kind regarding the contents or use of the information, including, but not l imited to, express and implied warranties of accuracy, completeness, merchantability, fitness for a particular use, or non-infringement. in no event will pmc-sierra, inc. be liable for any direct, indirect, special, incidental or consequential damages, including, but not limited to, lost profits, lost business or lost data resulting from any use of or reliance upon the information, whether or not pmc-sierra, inc. has been advised of the possibility of such damage. ? 1998pmc-sierra, inc. pmc-920702 (r5) ref 911105 (r13) issue date: july 1998 pmc-sierra, inc. 105 - 8555 baxter place burnaby, bc canada v5a 4v7 `604 contacting pmc-sierra, inc. pmc-sierra, inc. 105-8555 baxter place burnaby, bc canada v5a 4v7 tel: (604) 415-6000 fax: (604) 415-6200 document information: document@pmc-sierra.com corporate information: info@pmc-sierra.com application information: apps@pmc-sierra.com web site: http://www.pmc-sierra.com

▲Up To Search▲

Price & Availability of PM8313-RI

	To Download PM8313-RI Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .